At .NEXT 2017 US, Nutanix announced Xtract for VMs. Today it has been released.
You may have heard the news, the Turbonomic appliance platform has changed from openSUSE to CentOS. If you want to upgrade your appliance to version 6.0, then you must migrate to the new CentOS platform. You can stay on your openSUSE appliance, but you will hit the version ceiling of 5.9.1.
This post covers the process of migrating from the Turbonomic openSUSE appliance (version 5.9.1) to the Turbonomic CentOS appliance (version 5.9.0, upgraded to version 5.9.1). I also cover the final step of upgrading to Turbonomic 6.0 to get your hands on all of the great new features. Assuming you have a working knowledge of Linux administration, this will take approximately 60 minutes to complete.
- Login to vSphere Web Client.
- Browse to Home, System Configuration and select Nodes on the top left-hand corner of the UI.
- One of your PSC appliances or vCSA instances does not appear in the node list. You may see this after you have upgraded your vCSA infrastructure from 6.0 to 6.5.
- Or, the instance is listed with the message “The appliance management service on <object> is not running.”
Turbonomic has announced the release of version 6.0 of their Automation Platform. The most exciting part for me, is the new HTML5 UI is now fully functional and you no longer need to use the Flash-based UI (the “Classic UI” will still be present in the near future for the purpose of user transitioning). There are also some very impressive features for Public Cloud and Hybrid Cloud use-cases, particularly around cost-control of OpEx spending.
- You update your vCSA 6.5 instance to 6.5 U1a.
- After the update is completed successfully, the root Password Expiry Policy is enabled with 365 days, when it was previously disabled.
- This introduces operational risk to your environment where you could be locked out of the root account after a year has elapsed.
Update: VMware has informed me that this is a known issue to be corrected in a future update.
- vCenter Server deployed with Self-Signed Certificates.
- Login to vSphere Web Client.
- Try to upload a file to a Datastore and receive the message: “The operation failed for an undetermined reason. Typically this problem occurs due to certificates that the browser does not trust. If you are using self-signed or custom certificates, open the URL in a new browser tab and accept the certificate, then retry the operation.”
- Try to deploy an OVA file and the deploy OVA task hangs at 0% and must be cancelled.
What is NFV? These are virtualised Carrier/SP services that have historically run on dedicated, proprietary hardware in the field. A great example is an LTE Base-station controller or an MPLS Provider Edge router, where rather than buying the dedicated hardware appliance from the vendor, you buy the licence for the Virtual Appliance (NFV certified for use with vSphere) and deploy it in a vSphere cluster instead; which is much more efficient when you combine multiple NFV services in the same vSphere cluster.