标签：10.4 Server Director catalog Cloud vCenter VMware

请访问原文链接：https://sysin.org/blog/vmware-cloud-director-10/，查看最新版。原创作品，转载请保留出处。

作者主页：www.sysin.org

---

VMware Cloud Director 10.4 | 14 JUL 2022 | Build 20079248 (installed build 20079017)
VMware Cloud Director 10.3.3 | 2022 年 4 月 14 日 | 内部版本 19610875（已安装内部版本 19610595）
VMware Cloud Director 10.3.2 | 13 JAN 2022 | Build 19173640 (installed build 19173133)
(由于快照恢复操作导致数据丢失，VMware 于 2022 年 2 月 23 日从所有站点中移除了 VMware Cloud Director 10.3.2。)
VMware Cloud Director 10.3.1 | 2021 年 10 月 14 日 | 内部版本 18738799（已安装内部版本 18738571）
VMware Cloud Director 10.3 | 2021 年 7 月 15 日 | 内部版本 18296069（已安装内部版本 18295834）
VMware Cloud Director 10.2 | 2020 年 10 月 15 日 | 内部版本 17029810（已安装内部版本 17008054）
VMware Cloud Director 10.1 | 2020 年 4 月 9 日 | 内部版本 15967253（已安装内部版本 15967236）
vCloud Director 10.0 for Service Providers | 2019 年 9 月 19 日 | 内部版本 14638910（已安装的内部版本 14636284）

VMware Cloud Director Appliance 架构图

VMware Cloud Director Linux 安装架构图

什么是 VMware Cloud Director？

VMware Cloud Director 是一款领先的云计算服务交付平台，一些全球最受欢迎的云服务提供商利用它成功地运维和管理云计算服务业务。云服务提供商使用 VMware Cloud Director 向全球数以千计的企业和 IT 团队安全、高效地交付弹性云计算资源 (sysin)。

通过我们的云服务提供商合作伙伴在云环境中使用 VMware 产品，并通过 VMware Cloud Director 进行构建。

功能特性

多租户资源池化

基于通用基础架构轻松创建虚拟数据中心，以满足异构企业的需求。策略驱动型方法有助于确保企业拥有独立的虚拟资源、基于角色的独立身份验证以及精细的控制。

领先的云生态系统

遍布全球的多家领先云计算供应商均与 VMware Cloud Director 进行原生集成 (sysin)，支持云服务提供商交付独具特色的客户体验并抓住更多服务商机。

运维可见性和洞察信息

全新的仪表盘和单一窗口提供了集中式多租户云计算管理视图。利用 vRealize Operations 高级分析功能、计费功能以及与 VMware Cloud Director 的原生集成，深入了解企业环境。

自动化

VMware Cloud Director 与 vRealize Orchestrator、Terraform 和 Cloud Provider Pod 等领先的自动化工具深度集成，支持云服务提供商实现复杂工作流的自动化，并部署各种服务，同时还能保持访问控制和可见性。

多站点管理

跨站点和地理位置延伸数据中心；通过包含多站点聚合视图的直观单一窗口监控资源。

数据中心延展和云迁移

利用 VMware Cloud Director Availability 实现简单安全的虚拟机迁移和数据中心延展。支持真正的混合性、企业驱动型工作流、无缝连接以及冷迁移或热迁移选项。

容器即服务

对于要在同一虚拟数据中心内按需灵活利用容器和虚拟机，并希望缩短将 Kubernetes 投入使用所需时间的企业，VMware Cloud Director 提供了一个捷径。

计费

VMware Cloud Director 可提供成本透明度并落实财务责任，从而帮助 IT 负责人了解并优化顺畅支持业务服务所需的云计算基础架构成本。

更新说明

VMware Cloud Director 10.4 What's New

VMware Cloud Director version 10.4 includes the following:

• Networking Features

  Static Routing for NSX-T Data Center edge gateways. Both service providers and tenants can manually modify the routing table for an NSX-T edge gateway and to configure a static route within an organization VDC by specifying the network, next hop, and any specific networks or interfaces to which to direct traffic. If the specified next hop is part of an existing subnet that is associated with the edge gateway, you can specify a scope for the static route. A scope is an organization VDC network in which the next hop of the static route is located.

  Use static routing if you want to use a route that is not included in the routing table of your NSX-T edge gateway, or if you want to direct traffic trough a service edge gateway and a service interface, and to not use distributed routing. See Configure Static Routing.

  VMware NSX Advanced Load Balancer (Avi Networks) Feature set configuration at the service engine group level. All Controller instances that you register with VMware Cloud Director are now licensed and deployed with the Premium (also known as Enterprise) feature set. As a service provider, you can choose to restrict a tenant's feature set to Standard (Basic) at the Service Engine Group level.

  VMware NSX Advanced Load Balancer (Avi Networks) Standard feature set improvements for tenants

  • You can configure a single virtual service to use more than one port protocol.
  • You can configure multiple virtual services that are on the same edge gateway to be fronted by the same virtual IP address. The virtual services must use different ports.
  • You can use IPv6 for virtual IP addresses and for load balancer server pools.
  • You can configure a virtual service on the same subnet on which your load balancer is running.

• Fast Cross vCenter Server vApp Instantiation Utilizing Shared Storage

  This solution provides added flexibility for enabling fast instantiation of vApps from a catalog across vCenter Server instances. If a VMware Cloud Director catalog is backed by a VDC in vCenter Server A, instantiating a vApp from the catalog to a VDC backed by a cluster in vCenter Server B triggers a time-consuming OVF export-import process. In previous releases, the only way to avoid this was to ensure that the source and destination vCenter Server instances have shared storage, and the templates in the source vCenter Server reside on the same shared datastore where they are instantiated on the destination vCenter Server. Such configuration allows optimized copy of the templates, avoiding OVF export-import, and as a result leads to a significantly faster vApp instantiation. Starting with version 10.4, if vCenter Server A and vCenter Server B have a shared datastore and the templates reside there, VMware Cloud Director performs fast vApp instantiation to any destination datastore in vCenter Server B.

• Photon OS 3.0

  VMware Cloud Director appliance is now based on Photon OS 3.0 which brings improved security and upgraded OS packages.

• Service Accounts

  You can use VMware Cloud Director to create and manage service accounts for applications interacting with VMware Cloud Director. To provide continuous access to VMware Cloud Director, service accounts use OAuth refresh tokens instead of passwords. When using service accounts, applications cannot perform certain tasks and have only View rights for some resources, such as users, groups, roles, and rights. See Managing Service Accounts.

• Consolidated VM Console Proxy Endpoint

  VM console proxy traffic is now using the same IP and port as the VMware Cloud Director UI and API. In previous releases, the console proxy traffic used separate IP and port. The unified access point eliminates the need to manage an additional endpoint and certificate, and allows for SSL termination at the load balancer level. The VMware Cloud Director HTTP request log records the VM console traffic. You can enable the LegacyConsoleProxy feature, however, before enabling the legacy console proxy implementation, verify that your system configuration has the necessary console proxy settings and see After you enable legacy console proxy mode, the VMware Cloud Director cell on which you enabled the… and If you run the cell management tool's clear-console-proxy-settings command while legacy console pro….

• Enhanced trust management integration with vSphere

  VMware Cloud Director 10.4 enhances SSL connectivity to all vSphere infrastructure components, including ESXi, by incorporating the vSphere Certificate Authority (CA) into the VMware Cloud Director trust mechanisms which also affects previously added vCenter Server instances.

  IMPORTANT: Because of this enhancement to SSL connectivity, you must perform additional steps post-upgrade to ensure that VMware Cloud Director trusts all necessary vSphere certificates. Failure to perform these steps post-upgrade can disrupt the connection between VMware Cloud Director and vCenter Server instances.

  Follow the procedure outlined in the advisory that appears upon upgrade. See also KB 78885 and The VMware Cloud Director console proxy, uploading OVFs and media, and powering on a VM fail.

• VMware Cloud Director appliance certificate backup and restore

  1. In addition to HTTP and console proxy certificates, VMware Cloud Director Appliance backup includes a vcd_ova certificate and keys.
  2. VMware Cloud Director Appliance management UI supports optionally restoring the PostgreSQL and virtual appliance management UI certificates.

• IOPS Limits and Reservation Visibility Enhancements

  • Service providers can show or hide from tenants the IOPS limits and reservations on VM disks and named disks by using the new View Disk IOPS right. See Enabling the I/O Operations Per Second Setting.
  • VM disks and named disks views display both IOPS limits and reservations for each disk. VMware Cloud Director also returns the data in the corresponding API calls.
  • IOPS settings configured on a storage policy in vCenter Server appear in VMware Cloud Director named disk and VM disk views and in the corresponding API responses. By using the VMware Cloud Director UI, you cannot edit IOPS reservations and limits configured in vCenter Server.

• Catalog Enhancements

  1. If a catalog is subscribed to a published catalog, the synchronization of templates from the published to the subscribed catalog goes through a number of distinct steps. VMware Cloud Director now provides a detailed view of the currently running catalog synchronization task step and the progress percentage of that step. The currently running task step appears in the Recent Tasks panel and a more detailed view appears if a user clicks the Status of the item being synced. Distinct steps examples are: initializing library item sync, waiting for publisher to download files, transferring files from publisher to subscriber, importing OVF.
  2. When the catalog item synchronization task is at the Transferring files from publisher to subscriber step, clicking the task details shows the Active File Transfers tab where you can see the file transfer progress of individual disk files.
  3. If a catalog synchronization fails in file transfer phase due to VMware Cloud Director service restart or crash, when the cell restarts, the sync resumes from the previous transfer session, and VMware Cloud Director reuses the previously transferred content.
  4. If you deactivate the Automatically download the content from an external catalog setting of a subscribed catalog, at catalog creation, VMware Cloud Director does not sync the items within the catalog. VMware Cloud Director synchronizes only the item metadata. VMware Cloud Director synchronizes the VMDKs when you request a sync on each item. Moreover, if a publisher does not have the content downloaded, the catalog subscription with this option does not trigger download of VMDKs at the publisher side.

• API support for instantiating fenced vApp templates in NSX-T backed VDCs and for moving fenced vApps to VDCs backed by NSX-T Data Center

  You can use the VMware Cloud Director API to instantiate a vApp template that contains fenced networks into a VDC backed by NSX-T Data Center. You can also move a fenced vApp from a VDC backed by NSX Data Center for vSphere to a VDC backed by NSX-T Data Center.

下载地址

VMware Cloud Director 10.1.0：
百度网盘链接：https://sysin.org/blog/vmware-cloud-director-10/

VMware Cloud Director 10.2.0：
百度网盘链接：https://sysin.org/blog/vmware-cloud-director-10/

VMware Cloud Director 10.3.0:
百度网盘链接：https://sysin.org/blog/vmware-cloud-director-10/

VMware Cloud Director 10.4.0：
百度网盘链接：https://sysin.org/blog/vmware-cloud-director-10/

• VMware Cloud Director 10.4 - Virtual Appliance Installation or Migration
  File size: 1.42 GB
  File type: ova
  Name: VMware_Cloud_Director-10.4.0.8214-20079248_OVF10.ova
  Release Date: 2022-07-14
  Build Number: 20079248
  SHA256SUM: 741c67176aed7a70274c2d0b3107593393082ace1142efbd92228a8c9234a33f

• VMware Cloud Director 10.4 - Virtual Appliance Update Package
  File size: 714.4 MB
  File type: gz
  Name: VMware_Cloud_Director_10.4.0.8214-20079248_update.tar.gz
  Release Date: 2022-07-14
  Build Number: 20079248
  SHA256SUM: a878443aabb6d96e26a4cc3c681fc2694f35ca81fb534ed985ef7f5730740ba5

• VMware Cloud Director 10.4 - Binary for Linux Installation or Upgrade
  File size: 469.06 MB
  File type: bin
  Name: vmware-vcloud-director-distribution-10.4.0-20079248.bin
  Release Date: 2022-07-14
  Build Number: 20079248
  SHA256SUM: 262e6fef4a698bcf0e6b3369870c43cd2732a7b6d3532c0567a3c4e0eda3bd8a

标签：10.4,Server,Director,catalog,Cloud,vCenter,VMware
来源： https://www.cnblogs.com/sysin/p/16483277.html

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。