Intro
So, here we are. As most of you likely did, I eagerly awaited the release for quite some time. I successfully upgraded my lab standalone vRO appliance to version 9.0. The upgrade process was straightforward and seamless. It followed the same steps as before, as documented here.
During the upgrade, if vRO utilizes vCenter for authentication, the checker prompts you to provide vCenter credentials to update the PSC SSO metadata.
vro01 [ ~ ]# vracli upgrade exec -y --repo cdrom://
Loading update bootstrap.
Pre-upgrade check found that your Orchestrator server uses vSphere authentication. To be able to login with Orchestrator client we need to update metadata in PSC SSO https://vc.embl.de
Password for [email protected]: Update bootstrap loaded successfully.
Saving configuration parameters
Running procedures in background...
.......................................
Upgrade procedure started in background.
During upgrade, downtime of the services and restarts of the VAs are expected.
Use 'vracli upgrade status --follow' to monitor the progress.
... Preparing for upgrade .....................................
...............................................................
Running health check before upgrade for nodes and pods.
Health check before upgrade for nodes and pods passed successfully.
...............................................................
Configuring SSH channels.
SSH channels configured successfully.
...............................................................
Checking version of current platform and services.
Version check of current platform and services passed successfully.
...............................................................
Running infrastructure health check before upgrade.
Infrastructure health check before upgrade passed successfully.
...............................................................
Configuring upgrade repository.
Upgrade repository configuration completed successfully.
...............................................................
Saving restore point for artifacts. This might take more than an hour.
Restore point for artifacts saved successfully.
...............................................................
Shutting down services.
...............................................................
Saving system configurations.
System configuration saved successfully.
...............................................................
Saving restore point for data. This might take more than an hour.
Restore point for data saved successfully.
... Upgrade preparation completed successfully. ...
... Executing upgrade .........................................
...............................................................
Running additional health check before upgrade for nodes.
Health check before upgrade for nodes passed successfully.
...............................................................
Starting upgrade monitor.
Upgrade monitor started successfully.
...............................................................
Deactivating cluster of appliance nodes. This might take several minutes.
Cluster deactivation of appliance nodes skipped.
...............................................................
Configuring upgrade.
Upgrade is in progress. This might take more than an hour to complete and the system might be rebooted several times.Upgrade process logs
User Interface improvements
The System Settings section has an update. Several settings previously located in the outdated GUI (which was removed in version 8.18) and from vracli have been relocated to the Configuration Properties.
New Performance and Features section was added.
The UI has a nice UX improvement: when one of the settings is changed, a new popup window appears.
This means you don’t have to manually refresh the browser, restart sessions, or perform any other actions. Everything is handled automatically.
General improvements
- New plugin
VCF Operations Orchestrator Plug-In for VCF Automation for All Appswas added. - The standalone version now supports features such as Git, Roles, Environments, and Polyglot.
- No more
/vco, when accessing the vRO instance. - New section shows last runs.
Summary
I will continue my tests, but so far, everything appears to be in good working order and stable.
Take a look on a release notes before upgrading.
I also want to hear from you about how I can improve my topics! Please leave a comment with the following:
- Topics you're interested in for future editions
- Your favorite part or take away from this one
I'll do my best to read and respond to every single comment!
