This is important in order to understand limitations, known issues etc. The production environment I worked on was quite large so each step pretty much needed a maintenance window.I have seen setups where the upgrade would have broken the environment. So whilst the v Center and ESXi upgrade was scheduled for a later date, the v Shield Edges had sometimes a different idea.--remove below for the required contents of these files.For packages, this is preferable to using the --install option, as a format file can be installed without update-binfmts needing to be available. The first one for which execvp(3) succeeds will be used.When installing new formats, the --import action should be used instead. --install will attempt to enable this binary format in the kernel as well as adding it to its own database; see --enable below.You cannot install a format with any of the names ".", "..", "register", or "status", as these are used by the filesystem or the binfmt_misc module.update-binfmts manages a persistent database of these interpreters.When each package providing a registered interpreter is installed, changed, or removed, update-binfmts is called to update information about that interpreter.
So here I am trying to go for a whole upgrade process.
Some just died and had to be re-deployed, some customers “reset” their routed network, which also in turn re-deploys the Edges, and so on.
So by the time you actually get to the point of upgrading your v Center and ESXi, the majority of Edges have already been upgraded.
The main problems I always faced was getting to 5.1.x to begin with 🙂 There are a lot of articles out there in how to upgrade v Cloud Director 1.5 – but to be fair – the upgrade of v Cloud Director itself is quite straight forward.
It is just a matter of upgrading the binaries – which the installer does for you – upgrade the DB – which it says how to do – and that is it.