The Solution Add-On Landing Zone is a runtime defined entity that encapsulates the location of specific resources that are required for the unattended installation or upgrade of any solution add-on in VMware Cloud Director.

You configure your Solution Add-On Landing Zone by selecting a VMware Cloud Director organization to provide the resources for the Solution Add-On Landing Zone, a catalog where the solution add-ons are uploaded, and, if necessary, one or more organization VDCs.

If you don't use an organization VDC for your Solution Add-On Landing Zone, you will not be able to instantiate Solution Add-Ons that require backend services.

For each organization VDC that you select, you must specify the networks, compute policies and storage policies you want to attach to the solution add-ons. Additionally, each solution add-on can have a set of specific VMware Cloud Director configuration requirements that are defined as capabilities.

Prerequisites

  • Verify that you have enough compute and memory resources in each organization VDC or organization that you plan to use for the Solution Add-On Landing Zone.
  • Verify that the runtime lease for the vApps in each organization or organization VDC that you use for the Solution Add-On Landing Zone is set to Unlimited. For details, see Understanding Leases in VMware Cloud Director.
  • Create a catalog to store the .iso files of your solution add-ons in the organization that you plan to use for the Solution Add-On Landing Zone. When creating the catalog, if you are going to use an organization VDC for the Solution Add-On Landing Zone, toggle on the Pre-provision on specific storage policy option and from the drop-down menu, select the organization VDC that you will use. For details, see Create a Catalog in the VMware Cloud Director Tenant Guide.
  • Verify that each organization VDC network that you use for the Solution Add-On Landing Zone has access to the public service provider endpoints of the VMware Cloud Director API.
  • Verify that you either configured static IP pools or enabled DHCP for each organization VDC network that you use for the Solution Add-On Landing Zone.

Procedure

  1. In the top navigation bar, click More > Solution Add-On Management.
  2. Click Configure.
  3. In the What is a Solution Add-On Landing Zone page, familiarize yourself with the provided information, and click Next.
  4. In the General Settings page, select an organization to provide resources for the Solution Add-On Landing Zone.
    Important: Once you make this selection, you cannot change it.
  5. From the drop-down menu, select a catalog to store the .iso files for your solution add-ons.
  6. If you plan to deploy solution add-ons that use backend services, select at least one organization VDC and click Next.
  7. If you selected an organization VDC in which to deploy the backend services for your solution add-ons, click the vertical ellipsis () and click Configure.
  8. If you selected an organization VDC in which to deploy the backend services for your solution add-ons, select an organization VDC network to connect to your solution add-ons for each of the VDCs that participate in the landing zone.
  9. If you added an organization VDC to the landing zone, and you want to add more organization VDC networks, click Add Network and select a network from the list.
  10. If you added an organization VDC to the landing zone, click the Compute Policies tab and select a compute policy for the solution add-ons.
  11. If you added an organization VDC to the landing zone, click the Storage Policies tab and select at least one storage policy for the solution add-ons.
  12. Click Save and then click Next.
  13. Review your settings and click Finish.