vRealize Automation 8 supports sharing VMware Cloud Templates between projects.
During migration, you can migrate blueprints that are shared with existing projects. You can also maintain shared VMware Cloud Templates across projects even when the original project is rolled back. When the original project is rolled back, the cloud template ownership is transferred to another project.
To migrate shared blueprints:
Procedure
- Run a migration assessment on your vRealize Automation 7 source environment. For more information on how to run a migration assessment, see Run a Migration Assessment on a vRealize Automation Instance.
- Select the Infrastructure tab, select the first business group containing the blueprint, and click Migrate.
The migrated blueprints and their associated projects are seen on the
Design tab of
Cloud Assembly and as catalog items in
Service Broker.
- Navigate back to the Infrastructure tab, select the additional business groups containing the blueprint, and click Migrate.
In
Cloud Assembly, the cloud template is shown as only belonging to the first migrated project, but in
Service Broker the cloud template lists all projects in which it belongs.
What to do next
If you want to rollback the migration of the original business group and transfer blueprint ownership, navigate to the
Infrastructure tab, select the original business group, and click
Rollback. After rolling back the original business group, the cloud template ownership automatically transfers to the remaining migrated project associated with the cloud template. Any associated custom forms are also retained post rollback.
