Migrating to vRealize Automation 8, smooth ride or a nightmare?

-

 Step 1 - Deploy vRA 8

  • If you start fresh use the Easy Installer and skip the rest of this post
  • If you have vRA 7 hopefully you already have a vRSLCM and vIDM
    • If not, use the Easy Installer and we meet again in a few steps.
  • Deploy with vRSLCM is fairly straight forward and will take a few minutes of your time and a coffee break while deploying resources.
    • Prepare an FQDN and associate an IP as the deployment will make sure it has a reverse lookup.
    • You will need to create credentials in vRSLCM to go along with the deployment, tho this will mostly be used for accessing SHELL or vRO Configuration.
    • Pull out your license key and prepare a certificate and in about 10 easy steps you will have your vRA8 up and running.
Step 2 - Configuration vRA8

  • Login? vRA8 now relay on the external vIDM so go ahead and pull our the config_admin user credentials and login to System Domain.
  • Now for everyone familiar with vRA7, you will feel a bit lost at first, tho you will quickly recognize and feel a bit comfy once you start mapping old knowledge to new opportunities.
  • One of the first steps to make sure is your vIDM is mapped to the directory service in the same matter as vRA7. Make sure your sync has at least the same users and groups as you used to.
  • After you find and assign Organisation Owner rights to the proper users, go ahead and log in using your own login realm and safely store away the config_admin user.
Now is the perfect time to browse around for at least a few minutes to get a feel for the new looks and style.
 
Step 3 - vRA Migration Assistant
  • Add your sources vRA7 and vRO7, this is an easy task.
  • Start the assessment it will locate all your old tenants, business groups, and most bits and pieces available in vRA7.
    • Is it a "READY" state? - My guess is NO! If you have used vRA7 for some time there most definitely are a lot of things to look into fixing before migration.
  • Infrastructure first, let the joy begin, how to deal with this?
    • Endpoints - As we use an up2date vSphere infrastructure, this step was a "Ready"
    • XaaS - Blueprints
      • The migration does not anymore allow you to have XaaS blueprints pointing to IaaS Blueprints, so go ahead and reproduce your XaaS blueprints using IaaS Blueprints and Custom form.
      • This might take some time depending on the number of Blueprints your environment expose.
      • Also depending on the amount of XaaS Blueprints, this might need some tinkering with existing workflows you have published.
    • Approval Policy
      • There seems to be a bit of change to the approvals, and the methods we have used by adding checks on catalog item requests names weren't accepted anymore.
    • Build-in resource actions
      • Clear out Scale in and out, along with some of the Connect using VMRC and you should be in the clear here. This step requires you to alter possibly many Entitlements.
    • Custom Resources
      • Luckily we have used only resources that are supported in vRA8.2
    • Custom Reservations
      • Now, this says "Ready" but contains some fall pics.
        • Like did you enable alerts and the email field is empty?
        • Have you created reservations using the vRO reservation service, this might need a bit of tinkering. 
    • Blueprints
      • Now this step causing me a bit of a headache
      • We have used custom forms a bit, and there is a LOT of warnings, errors, and things to correct before advancing.
      • Making me think I will rather create new catalog items in vRA8 than migrate them.
      • This way we can make the best use of capability tags and not be stuck with old policies for placement.
    • Business Groups
      • Will move on smoothly to Projects
    • Custom resource actions
      • As with the XaaS Blueprints, these might need a bit of tinkering before moving on.

Kommentarer

  1. Anonym27. april 2022 kl. 08:56

    Migrating To Vrealize Automation 8, Smooth Ride Or A Nightmare? >>>>> Download Now

    >>>>> Download Full

    Migrating To Vrealize Automation 8, Smooth Ride Or A Nightmare? >>>>> Download LINK

    >>>>> Download Now

    Migrating To Vrealize Automation 8, Smooth Ride Or A Nightmare? >>>>> Download Full

    >>>>> Download LINK TC

    SvarSlett

Legg inn en kommentar

Populære innlegg fra denne bloggen

vRealize Automation 8 - Migration Assistant - Entitlements

-
While assessing the migration to vRA8 most definitely you will run into deprecated entitled actions or extensions. A lot of the internal VMware Actions or Extensions are no longer valid, here is a small list of common ones: Connect using SSH Connect using VMRC Connect using RDP Execute Reconfigure Cancel Reconfigure Scale In Scale Out Power Cycle ... A dirty quick fix is to loop all your entitlements before running the migration assistant and remove all of these deprecated if you do not depend on anyone using them in your vRA7 environment. var entitlements = Server.findAllForType("vCACCAFE:Entitlement"); for each (var entitlement in entitlements) { System.log(entitlement.name); var updated = false; var host = vCACCAFEEntitiesFinder.getHostForEntity(entitlement); var client = host.createCatalogClient().getCatalogEntitlementService(); var entitledResourceOperations = entitlement.getEntitledResourceOperations(); for each (operation in entitledResourceOperations) {
Les mer

vRealize Orchestrator and Microsoft Powershell Double Hops

-
Recently started automating Microsoft DNS and the best way in seems to be through Powershell . One of the common ways to deal with this is through a Powershell Host defined in vRO. You set it up securely with HTTPS and Kerberos and specify the credentials of a user with DNS server rights enough to see and manipulate the content of the zones and records you want to automate. So far so good, and you start developing the PowerShell commands you might need. Resolve-DnsName (Get-ADDomain).DNSroot -type ns | ? {$_.type -eq "A"} | select name,Address,IP4Address,IPAddress | ConvertTo-Json -depth 1 -Compress Get-DnsServerZone -ComputerName (Get-ADDomain).DNSroot Get-DnsServerResourceRecord -ComputerName (Get-ADDomain).DNSroot And they all work out nicely when you run them from your Powershell host, but once you run them from vRO in the Powershell session you run into the double-hop auth problem . There are many ways to deal with this, but often you need to thinker both with the Powers
Les mer

vRealize Orchestrator - SSH Keys - Idea for how to easy manage multiple keys

-
Many are using SSH to run commands something similar to  var  passwordAuthentication = false; var password = ''; var session = new SSHSession(hostName, username, port); session.connectWithPasswordOrIdentity(passwordAuthentication, password, path); Where the path leads to the private key file for the connection. Storing several key files in the vRO filesystem could easily lead to forget it when moving to a new vRO or add a new vRO node. Also when moving forward with vRO 8 it's less of a good idea to add elements to the local filesystem as a manual step. My suggestion for a solution is to make use of the vRO resource element. Store your key file as a vRO resource element, using the following step of code can runtime make the key available for SSHSession. var tempDirectory = System.getTempDirectory(); filePath =  tempDirectory + "/" + keyfile.name; keyfile.writeContentToFile( filePath ); Send the private key file as a resource to the action or workflow and you will h
Les mer