Blueprint Limitations
VMware Aria Automation
8 Migration
Assistant tool includes these limitations.- InVMware Aria Automation8, Blueprints are called VMware Cloud Templates.
- Nested blueprints (Parent blueprint with children blueprints) are not supported inVMware Aria Automation8. You can flatten nested blueprints, if desired. However, flattening blueprints will cause you to lose the abstraction layer.
- During migration, lease policies are migrated but theMinimum lease daysfield is not.VMware Aria Automation8 migrates minimum lease days asMaximum Lease Daysand maximum lease days asMaximum Total Lease.
- If your source Blueprint contained a reservation policy and that reservation policy is deleted before migration, the reservation policy is migrated and tagged on the VMware Cloud Template. However, when you attempt to provision a VMware Cloud Template (formerly Blueprint) inVMware Aria Automation8, it fails because the reservation policy does not exist and issues this error message during provisioning:To remediate this, open the VMware Cloud Template in"No placement exists that satisfies all of the request requirements. See if suitable placements and cloud zones exist for the current project and they have been properly tagged."VMware Aria Automation8 and remove the tag.
- When migrating blueprints, the Migration Assistant ignores NSX settings set at the blueprint level, such as Transport Zone and Networking Reservation Policy. When the migrated blueprint is deployed, the VM and Edge are placed in the same cluster.