vSphere 和 vCloud 是什么？
- 任何人都可以帮助我了解 vSphere n vCloud directer 吗？以及两者的区别？
- 安装后如何在自己的 Java 应用程序中使用 vCloud 的 REST URI？
- 任何使用 vCloud REST API 的 Java 示例都会非常有帮助..!! :-)
- Can any one help me in understanding vSphere n vCloud director? And difference in both?
- How to use vCloud's REST URI's in own Java application once it has been installed?
- Any Java example of using vCloud REST API will be really helpful..!! :-)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
vSphere 是VMWare 虚拟化平台的“基础设施”级别。 vSphere 是 IT 控制的虚拟化层； IT通过规划的vSphere架构精心构建网络、服务器和其他网络资源的虚拟化。
vSphere 构建在单独的 ESXi 服务器之上。这些服务器是类型 1 Hypervisor 虚拟化服务器。类型 1 虚拟机管理程序基本上是虚拟化特定的操作系统。 2 类虚拟机管理程序是在普通操作系统上运行的软件，用于支持正在运行的虚拟机。在第 1 类虚拟机管理程序（如 ESXi）中，整个操作系统旨在将物理服务器的资源专用于为虚拟机的执行提供优化的运行时环境的单一目的。
vSphere 的管理工具曾经称为 vCenter，它是一个客户端应用程序，但现在他们正在用 vSphere Web Client 取代它。这些工具通常由 IT 人员、管理员（如果您愿意的话）使用。这不是人们通常认为的“云”存在理由的动态分配资源的地方。 VMWare 文献称，vSphere 虽然已虚拟化，但仍然是静态、谨慎的 IT 领域。它不应该尝试对快速周转的供应需求做出反应，对于网络和主机等我们期望从云中获得的东西，因为这些快速周转与 IT/管理级别要求的谨慎法令背道而驰。
这就是 vCloud Director 的用武之地。该层位于 vSphere 之上，提供更流畅的调配模型。虽然 vSphere 可以保持稳定且变化缓慢，从而确保性能和安全级别符合企业系统的要求，但 vCloud 提供了一种模型，您可以在其中即时部署网络、服务器和其他资源。它位于 vSphere 之上的一层，因为它必须处于更高的级别，以便允许两个层都采用满足该层特定要求的配置模型； vSphere 需求侧重于安全性和性能方面的传统 IT 需求，而 vCloud 需求则主要涉及快速配置。我认为人们的困惑来自于不理解这些不同的要求。
为了从 Java 连接到任何 REST API，您只需要一种编程方式来进行 HTTP 调用。低级手段通常围绕客户端 API 构建，例如 HTTP 客户端。但是还有更高级别的工具，例如 Spring REST 模板。在更高级别，您可以使用 Java VMWare提供的SDK；这是一个非常好的选择，因为它允许您忘记整个 REST 方面并遵循 vCloud 资源的传统 Java 面向对象表示。 SDK 引用的 pdf 中有一个 Hello World 示例。
The vSphere is the "infrastructural" level of the VMWare virtualization platform. The vSphere is IT controlled layer of virtualization; IT carefully constructs the virtualization of networks, servers, and other network resources through a planned vSphere architecture.
The vSphere is built upon individual ESXi servers. These servers are Type 1 Hypervisor virtualization servers. A type 1 hypervisor is basically a virtualization specific OS. A Type 2 hypervisor is a software that you run on your normal OS to support running virtual machines. In a type 1 hypervisor, like ESXi, the whole OS is geared towards dedicating the resources of the physical server to the single purpose of providing an optimized runtime environment for the execution of virtual machines.
The admin tool for the vSphere used to be called vCenter, which was a client app, but now they are replacing it with the vSphere Web Client. These tools are typically used by IT folks, admins if you will. This is NOT where you go to get the dynamically allocated resources that folks normally think of as the raison d'etre of "the Cloud". The VMWare literature says that the vSphere, while being virtualized, is still the static, cautious realm of IT. It shouldn't attempt to react to the quick turn around provisioning demands, for things like networks and hosts, we expect from a cloud because those quick turnarounds run counter to the cautious edicts of the IT/admin level requirements.
This is where the vCloud Director comes in. This layer sits over the vSphere and provides a more fluid provisioning model. While the vSphere can remain stable and slow to change, thus ensuring levels of performance and security equal to the requirements of enterprise systsm, the vCloud provides a model in which you can instandly deploy networks, servers and other resources. It sits at a layer above the vSphere because it has to be a higher level in order to allow both layers to employe provisioning models that meet the specific requirements of the layer; vSphere requirements focus on traditional IT needs of security and performance while vCloud requirements are all about rapid provisioning. I think the confusion people have comes from not understanding these differeing requirements.
In order to connect to ANY REST API from Java you simply need a programmatic way to make HTTP calls. Low level means are typically built around a client API like HTTP Client. But there are higher level tools like the Spring REST Template. At an even higher level, you could use the Java SDK provided by VMWare; this is a very good option as it allows you to forget about the whole REST aspect and follow a traditionally Java object oriented representation of the vCloud resources. The pdf referenced for the SDK has a Hello World sample in it.
我对此也很陌生，但如果你还没有的话，这里是我收集的内容。 vSphere 是用于与 vSphere 服务器基础架构交互的 API。 vCloud API 用于与云管理层进行交互。 vCloud Director 或 vCloud Express 就是这样的例子。
这是我需要 vCloud 信息时的起点... http://communities.vmware.com/community/developer/forums/vcloudapi?sourceid=ie7&rls=com.microsoft:en-us:IE-SearchBox&ie =&oe=&rlz=
希望这有帮助。
I am new to this as well but here is what I gathered if you have not already. vSphere is the api that is used to interact with the vSphere server infrastructure. vCloud API is what is used to interact with their cloud management layer. vCloud Director or vCloud Express would be examples of this.
This is my starting point when I need vCloud info...http://communities.vmware.com/community/developer/forums/vcloudapi?sourceid=ie7&rls=com.microsoft:en-us:IE-SearchBox&ie=&oe=&rlz=
Hope this helps.