You upload the required file on PRISM console and ONE CLICK...
But with Life Cycle Management, its either of below -
1) Connect to internet which many organizations frown up regardless of the security or purpose. Nutanix knows this and also gave below option
2) Upload files via local web server.
But why increase the complexity by adding the need for setting up local web server?
Why not stick to upload file to PRISM as before?
Or am i missing the big picture or some other workaround?
Best answer by cameron
Right now, we control the firmware for Nutanix appliances so we can host those files (no need to manually upload your own BIOS update for example). LCM doesn't do Nutanix software or hypervisor upgrades yet - so that's why there isn't a need for the manual upload today. LCM in Prism Central will need a way to upload ESXi ISOs for example since they cannot be part of the official LCM bundle or internet hosted by us. Equally, you should be able to add any such files to your local LCM webserver for dark sites - so some form of manual upload needs to be supported.
At scale (say you have more than a few clusters to upgrade) it makes more sense to host all the files centrally somewhere and simply point LCM on each cluster to a location where all the binaries are held (eg. Prism Central or the webserver).... upload files once somewhere to be re-used by lots of clusters....We will be considering low bandwidth wan links (for ROBO clusters) as well - perhaps you need each ROBO site to have access to a local file repo (it may be quicker to send files via usb stick and pidgeon than some low bw/high latency satellite links for example).
The idea is that whether you have 1 cluster or 100s of clusters, the effort to upgrade software or firmware should be '1 click' easy - and we will need to take into account manual upload of certain files. Even if you have a mix of Nutanix platforms (NX or XC or HX) in your environment (different clusters), LCM needs to determine what you are running and provide the correct files without the admin having to read a manual or work out in what order upgrades need to happen.
Given that Prism Central is becoming more required as features grow in AOS generally, we think using it as a file repo seems to make a lot of sense for LCM. "Upload once, upgrade many" so to speak.