Rich over at VM/Etc and Duncan over at Yellow-Bricks both blogged about the fact that the VMware RCLI now does read/write to the free ESXi version. This is really great news. Prior to ESXi 3.5 U3 the RCLI was read-only meaning you could get a listing of portgroups for example but you couldn’t add any. This also broke some free scripts out there like the Quick Migration script I had written sometime back. I thought this was a little short sighted although I can understand some of the reasoning. I pushed hard with engineering and they understood my case and quickly worked to unlock the API all the way down the stack. Kudos to engineering for that quick work. Not sure why but you won’t find any press releases about this – just a few people picking it up on blogs. Just to show it working I have a few pictures from my lab here at the house.
This is a picture of one of my hosts. You can see it’s running ESX Server 3i, 3.5.0 Build 123629.
That’s the U3 build of the free ESXi. You can see the version in the download info on the free ESXi site.
A quick look at our current networking setup shows an out of the box configuration of the host.
We can use the RCLI to setup a new portgroup. Prior to U3 this would error out because you couldn’t write or change anything with the RCLI.
Now with U3 this actually does complete without any errors and you get the network configuration shown below.
Pretty awesome, huh? There’s a lot more you can do with the RCLI. Make sure to go take a look. If you come up with anything really cool make sure to comment back here how you’re using it.
NOTE: Make sure to read the update to this blog posting.
December 11th, 2008 at 7:31 pm
What about the VIMA? Doesn't it provide everything the RCLI does and more? And already works with ESXi?
December 11th, 2008 at 7:45 pm
VIMA, like the other API sets (VI Toolkit for Windows, RCLI, VIM SDK, etc) all hit the internal API set of ESXi. That toolset was locked down prior to U3 unless you had bought at least the Foundation SKU of Virtual Infrastructure and were managing it via Virtual Center. Once you had a VC license for the ESXi host then anything would work. If you were just using the free, standalone license then you only got read-only access. That all changes with U3 so you can now do read-write no matter which solution you're using.
December 11th, 2008 at 8:42 pm
Great to know. Does it mean there is no difference between the free version and licensed one?
December 11th, 2008 at 8:45 pm
Yup. No difference at all. Everything is just license key activated. All of the code is there though. Makes it real easy if you decide to step up later for the more advanced and useful features.
December 11th, 2008 at 9:49 pm
[...] Vote VMware RCLI now writes to ESXi Free Hosts [...]
December 11th, 2008 at 9:55 pm
[...] Vote VMware RCLI now writes to ESXi Free Hosts [...]
December 12th, 2008 at 4:36 am
[...] Vote VMware RCLI now writes to ESXi Free Hosts [...]
December 12th, 2008 at 5:19 am
Awesome Mike, nice work
December 12th, 2008 at 7:08 am
Sweet…this would definitely apply to the Windows PowerShell VI Toolkit as well, then.
December 15th, 2008 at 4:20 pm
I don't if it was working with U2 but I have tried it with U3. And it works well. You can backup / restore the ESXi configuration with
vicfg-cfgbackup.pl -s c:config.txt / vicfg-cfgbackup -f -l c:config.txt
December 15th, 2008 at 9:49 pm
[...] wrote a few days ago that the ESXi 3.5 U3 update unlocked the API set. Well, this was only partially true. I was just [...]
December 16th, 2008 at 3:37 am
[...] has been blogged all over the place that VMware has enabled the RCLI Read/Write on the latest update of ESXi, but it seems [...]
December 16th, 2008 at 5:19 am
I am little bit disappointed with RCLI – it is just like empty box, I wrote down some scripts for RCLI. And from my experience there missing some basic settings for deployment ESXi:
-rename existing portgroup (or edit VLAN)
-rename local storage – you can create local storage, for my surprise you cannot delete existing one – this influence another thing – easily set scratch partition – I find some workaround
-set nic failover order on vswitch, also on portgroup
so when I try to deploy 10 ESXi, I have to use UDA for pxe boot ESXi and unfortunatelly manually go through install process, then I execute RCLI scripts, then I need to set up rest – like failover order manually on all ESXi – uff really tough deployment..
December 16th, 2008 at 1:03 pm
[...] Update @ 12/14/08 – With version 3.5U3, VMware has thankfuilly decided to remove all API restrictions. See this article. [...]
September 1st, 2009 at 6:29 am
Is this read/write situation carried through to ESX 4i?
September 1st, 2009 at 12:29 pm
Is this read/write situation carried through to ESX 4i?