Blueprints are migrated to the target system and published to the vRealize Automation catalog as catalog items, with some exceptions.

The migration process creates a service named Infrastructure in the target system. Enabled blueprints are published to this service during migration. You can add services after migration is finished.

Blueprint management, including approval and entitlement management, has changed. For more information, see Changes from vCloud Automation Center 5.2 and Foundations and Concepts in vRealize Automation documentation. The Changes from vCloud Automation Center 5.2 PDF is available online with the 6.0 documentation.

Note:

Consider reducing the number of provisioning groups and special case blueprints before migration to keep the number of migrated entitlements to a minimum. In addition to the two standard entitlements, an entitlement is also created for each blueprint for which restricted access is configured.

The following considerations are helpful in understanding how blueprints are migrated.

  • Migration creates a single, default policy that is configured to require only the approval of the business group manager. The migration process adds the approval policy to each catalog item entitlement for each blueprint that had an approval configured in the source system.

  • Blueprint approval settings such as machine resource settings for CPU, memory, and storage are not migrated. However, approval information is captured in the pre-migration report. Reference the pre-migration report when you recreate approvals in the target vRealize Automation system.

  • ISO location information in the build profiles and blueprints and template information in the blueprints is migrated. However, you must reconfigure the ISOs and templates after migration to point to the system on which the manager service is running, for example a virtual machine or a load balancer. After migration is finished, recreate ISOs and templates that contain a guest agent.

  • Blueprints that are disabled are migrated but are not published to the catalog or listed as an entitled catalog item on the Entitlements page.

  • vCloud Networking and Security configurations are not migrated for multi-machine blueprints.

  • vCloud Director vApps and vApp components are migrated but only the vCloud Director vApp components are published.

  • The migration process creates a service named Infrastructure in the target system. Enabled blueprints are published to this service during migration. You can add services after migration is finished.

  • Global blueprints are published as shared blueprints.

  • Machine limits, lease information, and linked clone settings that are defined on blueprints and reservations are migrated.

  • If an approval setting or policy does not have an associated blueprint, it is not captured in the pre-migration report.

  • If a business group has no blueprints, the migration process does not create entitlements for that business group.

  • Blueprint icons are not migrated. Migrated blueprints use the default target system icons.

    The resolution at which source and target system blueprint icons are displayed differs. For better visual representation, recreate blueprint icons in the target vRealize Automation system at the recommended resolution of 100 x 100.