The vmware works okay because it refers to any product made by the company, but I've
always thought that application specific tags like vmware-player,
or a broad tag like virtualization would be more useful. However company tags can be helpful
from branching between different products made by the same company. Since there are 651 questions about
VMware Inc. products I think it justifies creation of at least some application specific tags. The big
ones being VMware Player, and VMware Workstation. If there is demand for it perhaps even component tags like vmware-tools.
What Happens To The VMware Tag:
I've noticed that the vmware tag now says not to use it, but I think it should be re-instated.
It serves a very different purpose from program tags like vmware-player, or
topic tags like virtualization. It's company specific, which can be helpful for branching around
between a company's different products. It's certainly nowhere near as useful as a topic tag, or a program tag.
So I don't think it works well as a primary tag, but I see no reason why (when possible) it couldn't be used
as a final addition. Eg: virtualizationvmware-playervmware . I would suggest if possible though
that it be changed to vmware-inc as that is their name according to their copyright at the bottom of their
Corporate Naming Schemes:
A corporate name is generally made up of three parts: "distinctive element", "descriptive element", and a legal ending.
All corporations must have a distinctive element, and in most filing jurisdictions, a legal ending to their names.
A Better General Tag:
Not to hijack the thread, but I would also like to put forth the previously mentioned virtualization
tag even though there are already tags vmware, virtual, and vm. This tag would serve a wider
audience than the company specific vmware, is more specific than virtual,
and is slightly broader than vm. The virtualization tag can could work in
harmony with the program specific tags of any virtualization product, but would also be helpful for questions
that don't yet have a product tag. Much like the security tag, the virtualization tag would allow for
branching between different virtualization products. For example a question could be tagged virtualization
virtualbox, and another virtualizationvmware-player. This says "Hey I'm a question about virtualization,
but more specifically about virtualization with this product".
Getting The Names Correct For VMware Products:
My biggest concern with creating application specific tags for VMware Inc. products would be making sure to get
the names correct.
VMware Inc. often refers to the same product by multiple abbreviated/altered forms of the name within their
articles, and documentation. For Example "VMware"
is typically in the name of their products, but often you will read one article that says "VMware Whatever",
and then another that just says "Whatever". You may even see this within the same article!
VMware vMotion in VMware vSphere 5.0: Architecture, Performance and Best Practices
Using VMware vSphere® vMotion® automated migration capability, you can schedule migrations at pre-defined times,
without administrator intervention.
In these examples I believe that VMware vMotion is the correct name, because VMware Inc typically has VMware
in the product name, and because in the below example the name bears the trademark symbol, and the registred
VMware® VMotion™ enables the live migration
of running virtual machines from one physical
server to another with zero downtime, continuous
service availability, and complete transaction
The ESX Tag:
I've never used VMware's high end products, but my understanding is that ESX and ESXi are
architectures used by VMware ESXi, and VMware ESX both of which are hypervisors that act as
component applications of VMware vSphere and some other products like VMware View.
ESX & ESXi Architectures:
Learn more about the differences between ESX and ESXi hypervisor architectures.
VMware ESX & VMware ESXi Hypervisors:
VMware ESX and VMware ESXi are both bare-metal hypervisors that install directly on the server hardware.
Both provide industry-leading performance and scalability; the difference resides in the architecture
and the operational management
vSphere is a sophisticated product with multiple components to install and set up.
ESXi can be installed in several ways. To ensure the best vSphere deployment, understand the options
thoroughly before beginning the installation.
In this [ https://my.vmware.com/web/vmware/info/slug/desktop_end_user_computing/vmware_view/5_0 ] link you can
see VMware ESXi listed as part of the download for VMware View 5 Premier Edition.
I see no reason to create architecture specific tags like esx and esxi
since to my knowledge it is only supported by Vmware Inc. in VMware ESX and VMware ESXi
and therefore questions about ESX/ESXi will always be about VMware ESX/VMware ESXi, or off-topic.
I think if you are only going to create one tag then vmware-vsphere,
would make more sense than esx because it covers the entire product. Additionally the esx tag
currently refers to VMware ESX which as discussed is different from ESX. Potentially several tags could be made if
there were enough questions to justify them, which doesn't appear to be the case at the moment. There is a huge
mass of VMware vSphere component programs like VMware vMotion, VMware vSphere Update Manager, VMware ESXi,
VMware ESX, VMware vSphere Client, and VMware vSphere Web Client. Don't forget about features within the progams
like ESXi Shell, and so forth.
VMware vSphere Update Manager:
VMware vSphere® Update Manager™ automates patch management and eliminates manual tracking and patching of
vSphere hosts and virtual machines.
VMware vSphere Web Client:
Client Interfaces for vSphere
You have several ways to access vSphere components through vSphere interface options.
vSphere interface options include: vSphere Web Client
An ESXi system includes a direct console that allows you to start and stop the system and to perform a
limited set of maintenance and troubleshooting tasks. The direct console includes the ESXi Shell.
The ESXi Shell includes a set of fully supported ESXCLI commands
As mentioned before the VMware ESXi component program is not limited to VMware Sphere. So there is potential for some
other tags like VMware View, and VMware Horizon.
VMware Player & VMware Player Plus
I forgot to write about this, so I'ved edited it in. There are actually different versions of VMware Player. For example there is the freely available VMware Player for private use, there is the purchasable VMware Player Plus for private or commercial use, and there is the VMware Player that comes accompanied by VMware Workstation that is modified to allow installation on the same machine. Would these all be covered by the same tag?
VMware Player is free for personal non-commercial use. If you would like to learn about Virtual Machines or use them at home you are welcome to use VMware Player for Free.
VMware Player Plus:
VMware Player Plus is designed to be used commercially.
VMware Player Plus supports restricted virtual Machines
Per-incident support offerings are available to VMware Player Plus customers
VMware Player (From VMware Workstation):
Can I commercially use the copy of VMware Player that comes with VMware Workstation?
Yes, you can commercially use the copy of VMware Player that comes with VMware Workstation. It must be run on the same machine VMware Workstation is installed on.
I think creating application specific tags is a great idea. My only concern would be making sure
they are named correctly by checking for publications of the name bearing the Trademarked and Registred Trademark
symbols in VMware Inc.'s
documentation and articles. Additionally I would suggest a new broad tag should be implemented such as virtualization, because
there is no point in creating tags for every VMware Inc. application ever made unless there are questions for them. I don't
see any reason why the vmware needs to be gotten rid of as it works well for creating company based branches.