vCloud Suite Deployment Configurations---vCloud 部署配置

原文：

Client applications developed by using the vCloud Suite SDK work against the vCloud Suite environment configured for your needs. Depending on the size of the vCloud Suite environment, you can use three deployment configurations: embedded, centralized, and mixed.

Embedded Deployment Configuration

For small environments, such as development and test, you can install vCenter Server with an embedded Platform Services Controller on a single virtual machine or physical server. Such a deployment configuration is called embedded. The services provided in an embedded configuration have distinct endpoints within the same domain, and a client must execute the same procedures to look up, authenticate, and establish sessions with the vCloud Suite services API endpoint.
vCloud Suite Deployments: Embedded Configuration

Centralized Deployment Configuration

For larger virtual environments, vCenter Server with an external Platform Services Controller deployment is most suitable. You use the centralized deployment configuration to separate the Platform Services Controller and vCenter Server and have them installed on different hosts. The centralized configuration includes one or several Platform Services Controller instances that provide common services to support a number of vCenter Server instances.
A client must first connect to the Lookup Service residing on the Platform Services Controller with a previously known URL and retrieve the vCenter Single Sign-On service endpoint and the vCloud Suite services endpoints.
vCloud Suite Deployments: Centralized Configuration

Mixed Deployment Configuration

Your virtual environment can have more than one Platform Services Controller that can be deployed using both configurations: embedded and centralized. This type of deployment configuration is called mixed. Having a mixed deployment ensures high availability on your vCloud Suite environment. During a mixed vCloud Suite deployment, you replicate the infrastructure data across all vCenter Single Sign-On services residing on the different Platform Services Controller instances. As a result, the data across the vCloud Suite infrastructure is synchronized so that the content is the same across all Platform Services Controller instances.
vCloud Suite Deployments: Mixed Configuration

翻译：

客户端应用程序开发是使用vCloud SDK，而vCloud是基于vCloud 生产环境配置和用户需求。             
根据不同大小的vCloud环境，您可以使用三部署配置：嵌入式，集中，和混合。

嵌入式：
对于小的生产环境，比如生产环境只用于开发和测试，你可以在单一虚拟机和物理服务器安装vCenter服务器和嵌入式平台服务控制器。
这样的部署配置为嵌入式。在嵌入式部署提供的服务中在同一个域中有不同的端点，一个客户端必须执行相同的程序去查找、验证并与vCloud 服务端点API 建立会话。

集中式：
对于较大的虚拟环境，VCenter服务器与外网平台服务控制器部署在一起是最合适的。
你使用集中式部署可以使VCenter和平台服务控制器分离开，部署在不同的主机上。
集中部署包含一个或多个平台服务控制器，它们可以支持多个VCenter服务器提供公共服务。
客户必须首先连接到查找服务驻留在与先前已知的URL平台服务控制器，检索vCenter单点登录服务端点与端点的vCloud服务。


混合模式：
你的虚拟环境可以部署超过多台平台服务控制器，你就可以使用两种部署方式：嵌入模式和集中模式，这种类型的部署配置称为混合模式
如果vCloud 生产环境部署的为混合模式，如果你复制基础数据的话，这些基础数据来源于生产环境中所有VCenter 单点登入服务居留的不同平台服务控制器实例。
因此，在VCloud生产环境中基础数据是同步，不同平台服务控制器共享相同的基础数据