Using the vRealize Automation 8 Migration Assessment Service 21 Feb 2020 vRealize Automation 8.0
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Using the vRealize Automation 8 Migration Assessment Service
21 Feb 2020vRealize Automation 8.0
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
If you have comments about this documentation, submit your feedback to
VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com
Copyright © 2020 VMware, Inc. All rights reserved. Copyright and trademark information.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 2
Contents
1 Using the vRealize Automation 8 Migration Assessment Service 4
2 Run a Migration Assessment on a vRealize Automation Instance 5
3 View Assessment Results 8
4 Considerations About vRealize Automation Cloud 9System Objects 9
Blueprint Objects 10
Endpoints 10
Using Legacy Extensibility 11
vRealize Orchestrator Plugins 12
Postgres and Microsoft SQL Server Database Access 12
Writing Workflows and Action Code for vRealize Automation Cloud Assembly 12
Using Subscriptions in vRealize Automation Cloud Assembly 13
VMware, Inc. 3
Using the vRealize Automation 8 Migration Assessment Service 1The ability to upgrade or migrate from vRealize Automation 7.5 or 7.6 to vRealize Automation 8.0 is not supported in vRealize Automation 8.0.
Currently, you can only perform a migration assessment on your source environment and any embedded vRealize Orchestrator instances to determine the migration readiness of your vRealize Automation 7.5 or 7.6 source environment. The migration assessment alerts you to any system object and its dependencies that are not ready for migration and that will impact your migration process in the future. See Chapter 4 Considerations About vRealize Automation Cloud.
When migration becomes available in future releases, content and configuration data from your current vRealize Automation 7.5 or 7.6 source environment will be moved to a target deployment of vRealize Automation 8.0.
VMware, Inc. 4
Run a Migration Assessment on a vRealize Automation Instance 2Using the migration assessment service, you can run a migration assessment on a single vRealize Automation 7.5 or 7.6 instance to determine migration readiness.
The migration assessment includes connecting to your vRealize Automation source instances and assessing the vRealize Automation and embedded vRealize Orchestrator instances.
VMware, Inc. 5
The migration assessment reviews your vRealize Automation source environment and identifies what objects to carry over and migrate. You can review the assessment results and correct items in your source environment that are not correctly set up or ready for migration in the future.
Procedure
1 From the Source Instance page, Click Add a Source Account.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 6
2 Select a vRealize Automation or vRealize Orchestrator source type.
3 Enter the credentials of your vRealize Automation 7.5 or 7.6 or vRealize Orchestrator source environment.
Note You must provide a FQDN or an IP address for the source in the hostname text box. For example, test-n-88-087.test.vmware.com
4 Click Validate and Save to validate and identify all the tenants that are available for migration.
Note You must provide the system administrator and password of your source environment to identify all available tenants.
5 In Allow migrations from these tenants, toggle and select which tenants you want to assess in vRealize Automation 8.0.
6 Click Save to finish the migration assessment of the selected source tenants.
Results
Your source environment is assessed for migration readiness. You can view the details of the source enviroment configuration on the source instances page. Additionally, you can export the assessement report to your local drive by clicking Export on the source instance's tile.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 7
View Assessment Results 3After running a migration assessment on your source instance, you can view the results.
The assessment results are itemized into categories on the Assessment tab:
n Infrastructure
n Subscriptions
n Deployments
The assessed business groups are listed with their status:
n Ready - Business group is ready for future migration. No action is needed for migration readiness.
n Ready with warnings - Business group is ready but needs review. Remediate any issues that might impact migration.
n Not Ready - Business group is not ready for migration. Review details of the business group in your source environment and correct areas needing attention.
n Assessing - Business group is still being assessed for migration readiness.
n Assessment failed - The assessment failed, retry assessment.
If applicable, after modifying any business groups listed as not ready or ready with warnings, click Update to update its status in the assessment results table.
VMware, Inc. 8
Considerations About vRealize Automation Cloud 4vRealize Automation Cloud introduces various functional changes.
Although migration to vRealize Automation Cloud is not supported, when planning to migrate your source environment in a future release, you can review how your 7.x concepts will be converted.
You should review the changes that vRealize Automation Cloud introduces to best prepare your source environment for future migration.
This chapter includes the following topics:
n System Objects
n Using Legacy Extensibility
System ObjectsSystem objects are named and stored differently than in vRealize Automation 7.5 and 7.6.
VMware, Inc. 9
The following system objects are stored in a new format:
n Blueprints
n Endpoints
Blueprint ObjectsWhen comparing your vRealize Automation 7.5 or 7.6 source to your new vRealize Automation environment, the blueprint object types are different.
Table 4-1. Blueprint Types
Type vRealize Automation 7.5 or 7.6 vRealize Automation 8.0
vSphere (vCenter) machine Infrastructure.CatalogItem.Machine.Virtual.vSphere
Cloud.vSphere.Machine
AWS Infrastructure.CatalogItem.Machine.Cloud.AmazonEC2
Cloud.AWS.EC2.Instance
Azure Machine Cloud.Azure.Machine
Generic Virtual Machine Infrastructure.CatalogItem.Machine.Virtual.Generic
Cloud.Machine
On-Demand Load Balancer (NSX) Infrastructure.Network.LoadBalancer.NSX.OnDemand
Cloud.NSX.LoadBalancer
On-Demand Routed Network (NSX) Infrastructure.Network.Network.NSX.OnDemand.Routed
Cloud.NSX.Network
NSX-T On-Demand Routed Network Infrastructure.Network.Network.NSXT.OnDemand.Routed
Cloud.NSX.Network
NSX-T On-Demand NAT Network Infrastructure.Network.Network.NSXT.OnDemand.NAT
Cloud.NSX.Network
Existing Network Infrastructure.Network.Network.Existing Cloud.vSphere.Network
On-Demand Private Network (NSX) Infrastructure.Network.Network.NSX.OnDemand.Private
Cloud.NSX.Network
Puppet ConfigManagement.Puppet Cloud.Puppet
Ansible
Note vRealize Automation 7.5 and 7.6 supports Ansible Tower but vRealize Automation 8.0 only supports Ansible.
ConfigManagement.Ansible Cloud.Ansible
EndpointsEndpoints are added and supported differently than in previous vRealize Automation versions.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 10
Table 4-2. vRealize Automation 8 Supported Endpoints
Endpoint Added as ...
Azure Added as a cloud account.
AWS Added as a cloud account
vCenter Added as a cloud account
NSX-T Added as a cloud account
NSX-V Added as a clound account
Puppet Added as an integration account
Ansible Added as an integration account
IPAM Added as an integration account
vRealize Orchestrator Added as an integration account
Unsupported EndpointsvRealize Automation 8.0 does not support:
n Openstack
n vCloud Air
n vCloud Director
n vROps
n Proxy
n Netapp ONTAP
n Hyper-V (SCVMM)
n KVM (RHEV)
n VCH Endpoint
Using Legacy ExtensibilityIn a future release, when migrating, the extensibility functionality will be hosted in the vRealize Automation Cloud Assembly service and managed by the Event Broker.
Depending on your source environment, you might need to modify existing workflows and action code to optimize extensibility in vRealize Automation 8.0. Modifications and new functionality include:
n vRealize Orchestrator plugin support
n Postgres and Microsoft SQL server database access
n Rewriting workflow or action code for use with vRealize Automation Cloud Assembly
n Using subscriptions with vRealize Automation Cloud Assembly
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 11
vRealize Orchestrator PluginsSeveral vRealize Orchestrator plugins are not supported in vRealize Automation.
These plugins are no longer supported:
n vRealize Automation CAFE plugin
n vRealize Automation .NET plugin
n vRealize Automation REST Plugin
You must rewrite all custom content in vRealize Orchestrator to use the new vRealize Automation 8.0 API interface. Implementations that rely on API calls to vRealize Automation using the REST plugin must be rewritten.
For information on writing workflows that require a reduced effort to refactor, see Writing Workflows and Action Code for vRealize Automation Cloud Assembly.
Postgres and Microsoft SQL Server Database AccessAccess to the Postgres and Microsoft SQL Server databases are not supported.
In a future release, to minimize problems during migration or upgrade, use the supported API interfaces.
Note Currently, there is no guidance for correcting direct database queries between vRealize Automation versions.
Writing Workflows and Action Code for vRealize Automation Cloud AssemblyUsing these best practices, you can write extensibility code and workflows to easily interact with vRealize Automation Cloud Assembly.
Use Payload from Event BrokerWhen writing or coding content to work with vRealize Automation Cloud Assembly, use the content provided in the Event Broker payload instead of calling vRealize Automation for information. It is a common practice to ignore the payload passed into the workflow and query the same information from vRealize Automation. In vRealize Automation Cloud Assembly, you subscribe vRealize Orchestrator workflows to call all required workflows for the state.
In doing so, the amount of refactoring required is reduced because updates are only needed to the parent workflow.
Do Not Pass vRealize Automation Plugin Objects into Sub-Workflows or ActionsDo not pass vRealize Automation plugin objects into elements that do not call the vRealize Automation plugin but instead, pass the specific information that the element requires to perform. For example, instead of passing a virtual machine object to an Action that requires only the virtual machine's name, pass the virtual machines name as a string.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 12
Using Subscriptions in vRealize Automation Cloud AssemblyIn a future release, when migration is available, you will use migrated vRealize Automation 7.5 or 7.6 extensibility in vRealize Automation Cloud Assembly with these subscriptions accordingly.
Table 4-3. Subscriptions in vRealize Automation Cloud Assembly
Subscription Use
Blueprint component completed Use as required.
Blueprint component requested Use as required.
Blueprint configuration Use as required.
Blueprint request completed Use as required.
Blueprint requested Use as required.
Business group configuration Use as required.
Catalog request completed Use as required.
Catalog request received Use as required.
Component action completed Use as required.
Component action requested Use as required.
Deployment action completed Use as required.
Deployment action completed Use as required.
Endpoint Action Limit use
EventLog default event Limit use
Infrastructure endpoint test connection Do not use.
IPAM IP lifecycle event completion Limit use
Machine lifecycle Limit use
Machine provisioning Use only:
n BuildingMachine
n MachineProvisioned
n Disposing States
Orchestrator server configuration Do not use.
Orchestrator server configuration (Xaas) - Obsolete Do not use.
Post-approval Use as required.
Pre-approval Use as required.
Resource Reclamation Completion Event Do not use.
Using the vRealize Automation 8 Migration Assessment Service
VMware, Inc. 13
Related Documents
