5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
That information provided by the OP are the non-default settings. If the setting is not listed, then you can leave it as default or set it to your customer preference.
As I stated in the original post:“I know that updating NGT via Prism Central works pretty well for Windows, but once again, it fails miserably for Linux (at least OUL).” I was putting it out to the community, because www.nutanix.dev is lacking as well. I will go ahead and accept the answer as “no there isn’t anything. Good luck with your Linux upgrades on your own.”
If this is Nutanix Feature that can be implemented. Feel free to open Product Improvement case. Are you aware of what Ansible is?
There are a few different methods that you can go with on this. What I personally found that works with least amount of downtime is to do something similar to the alternative method: Move all of your VM’s to 1 cluster (assuming it has capacity) Run the in-place conversion (Convert Cluster) utility in Prism to switch it to AHV. Trust me, it works well! Use “Nutanix Move” to move your VM's from the ESX cluster to the AHV cluster. It’s a little tedious, but it can handle the driver installations for you and you can reboot the VM on your schedule when you cutover. After all VM’s are moved over, convert the other cluster to AHV. This process gives you a solid rollback option to VMware if AHV doesn’t work out for you. Make sure your VM’s can support AHV. If you have any OVA’s, check for a KVM-version of the appliance. I know there are many different ways that you can do these conversions. Your account team would probably be able to help you go through all of the details within y
Firstly, I am running the enterprise 5.10.9 version for the lab, and not CE. Sorry for not being clear about that. Also, I see that when I first wrote the post, I messed up my original description. I was able to “successfully” convert the cluster from AHV back to ESXi with the help of Support, since genesis was bombing out on network configurations it thought had changed, but had not to the best of my knowledge. After getting it back to ESXi, LCM and other software upgrades were not working anymore due to network configuration issues. That was when I decided to just save our test VM’s and re-foundation the cluster. 2 nodes made it fine with just having to add the /firstboot directory so Foundation could do its thing (which may be an ENG that was fixed in 4.5.2). The 3rd node is the one that had a weird pathing issue. Jeremy, I see you found the case I opened yesterday. I am doing the boot-from-phoenix now and installing the CVM. Once that is complete, I’ll manually run the clus
Yes, after the migration, we would plan on reducing down to a single storage container, especially considering we will be investigating a conversion to AHV after the migration. We just wanted to make sure that creating multiple containers to workaround VMWare's limits would be a viable option without cratering the cluster/storage pool. Thanks
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
