We installed ESX 3.0.1 and found that it is Linux-based. Unfortunately, no one at our shop knows a stitch about Linux. Do we need to know Linux to use the ESX 3 product or not?
TIA,
Bill
P.S. I have nothing against learning about Linux but at this moment (for our ESX 3 test) we are not familiar with it.
fyi....if you are interested in learning some basic Linux, here are some good links.
Windows to Linux roadmap - http://www-128.ibm.com/developerworks/linux/library/l-roadmap.html
From DOS/Windows to Linux HowTo - http://www.tldp.org/HOWTO/DOS-Win-to-Linux-HOWTO.html
Universal Command Guide for Operating Systems - http://www.allcommands.com/
While it is certainly helpful, it isn't required. Once installed, you do your management through the Virtual Infrastructure Client - This is where you create the Virtual Machines..etc.
Yes and no.
Usually most things for daily business can be done through the VI Client (GUI). Everything else is usually documented in VMware's manuals. So it's basically typing what you have there.
When it comes to troubleshooting it's certainly a plus to have some Linux basics.
Anyway: Start with it and get comfortable with the commands slowly. If you know DOS and know how to type you will have fun in the Console too.
cheeko
Bill,
Being that the ESX product is based on Linux - I would say it is important to know at least something about the Linux operating system.
For the most part, you will be either using the web interface or The client application which require no knowledge of Linux. I have been using ESX for over a year in production. The only time I have used the Linux console is for import/export (manual backup) of VMs. This is not the only backup method - it just works for me. Additionally, you may use the console for troubleshooting purposes. However, if you have a support contract that shouldn't be an issue.
So, long story short, I would say that Linux knowledge isn't necessary - but it would help.
ESX is not based on Linux and VMware would get very upset if they heard you say that. It's just the Service Console that's based on Linux (RHEL3), and that's really just a 'special' virtual machine, the vmkernel itself is written completely from scratch by VMware.
As for needing Linux knowledge to manage an ESX environment, not essential, but very helpful I would say.
mittell,
Although I see your point - I do not see how you could say that VMware is not based on linux. I certainly agree that there are many pieces created "from scratch" by VMware. However, the operating system is certainly not proprietary as it supports custom tools and enhancements.
How is that not linux or linux-like?
Because you're only seeing the Service Console, which is Linux, but it is not the hypervisor - which is the vmkernel and exists underneath the Service Console. The vmkernel is entirely proprietary.
Think of the Service Console as a boot loader / device manager, it doesn't have anything to do with the virtualisation layer, and it actually is itself a virtual machine - just a special one.
mittell,
Point taken. I learned something else new about virtualization today!
-bill
Bill -
It's the hypervisor that vmware wrote that the linux service console runs on.
Mittell you tell him
fyi....if you are interested in learning some basic Linux, here are some good links.
Windows to Linux roadmap - http://www-128.ibm.com/developerworks/linux/library/l-roadmap.html
From DOS/Windows to Linux HowTo - http://www.tldp.org/HOWTO/DOS-Win-to-Linux-HOWTO.html
Universal Command Guide for Operating Systems - http://www.allcommands.com/
Check Mike's guides out:
http://linuxweb-1.griffin.net.uk/~rtfmed/?page_id=7
In particular, page 8 of the Guide to ESX 3 Service Console has a list of linux commands and examples that are nice to know.
I would also recommend setting up a linux box (maybe even a virtual machine) just to play around with. Everyone else is right, 95% of what you want to do can be done with the GUI. It's that extra 5% that it is nice to know these commands.
Just to give you an example, I have to hard set the speed and duplex of my NICs - sometimes Virtual Center can't even connect to the box to change that. So my only choice is to set it from the command line.
FYI - I knew basically no Linux before I started with VMware.
fyi...see this post also...
http://www.vmware.com/community/thread.jspa?messageID=625255򘩧