Chinaunix首页 | 论坛 | 博客
  • 博客访问: 947417
  • 博文数量: 276
  • 博客积分: 4182
  • 博客等级: 上校
  • 技术积分: 4486
  • 用 户 组: 普通用户
  • 注册时间: 2012-04-17 21:14
文章分类

全部博文(276)

文章存档

2014年(9)

2013年(132)

2012年(135)

分类: 系统运维

2013-10-08 11:38:04

我觉得这是一个相当不错的关于这一主题理解问题还是来了曾经在一段时间VI的Java API社区和我的收件箱有些人得到了错误,而试图通过API管理ESXi服务器API免费ESXi的支持是有限的准备仅根据一个VMware知识库文章

vCLI, PowerCLI, and vSphere SDk for Perl are limited to read-only access for the free vSphere Hypervisor edition. To enable full functionality of vCLI on a VMware ESXi host, the host must be licensed with vSphere Essentials, vSphere Essential Plus, vSphere Standard, vSphere Advanced, vSphere Enterprise, or vSphere Enterprise Plus.

Note:

  1. The vSphere Hypervisor mentioned is the ESXi.
  2. It’s not limited to vCLI, PowerCLI, and vSphere SDK for Perl, but any other like VI Java API. They all built on top of vSphere SDK for Web Services, therefore have the same limitation.
  3. You can find comparisons of ESX and ESXi 4.0, 3.5.

To use full vSphere API/CLI with ESXi, you got to have a license. So if you have issue with API calls or CLI scripts, don’t forget to check your ESXi server license.

As a side story, the API was once unlocked unintentionally due to a bug fix on free ESXi 3.5 U3 as covered by Mike in his blog. Check it out here.

阅读(3958) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~