Hi Team,
we want to adopt a new specification for version numbering of our plugin. We want to specify the version numbering as "A.B.C.D.E" for example “9.6.0.0000.1”, “9.6.1.0100.1”, “9.6.1.0101.1”, “9.6.1.0001.1”. where E=build version, then how does this version work for:
- Fresh plugin extension registration
- Upgrade plugin extension from previous release version TO next release version
- Upgrade plugin extension from nightly/dev build TO nightly/dev build
- Criteria of version string for plugin extension upgrade?
When I refer the exisitng vSphere plugin, I'm seeing two version numbers in the mob.
When I see the VC packages, it seems the virgo server is taking the Version#1 as the criteria to download the plugin package to vCenter server.
1. In my obsevation, I 'm assuming that vSphere mob will blindly fetch the version for mob and downloads the same to "vc-packages" if the same version is not found in the directory.
vSphere doesn't do any comparision like 6.6.1.20000>6.6.1.19998. Please confirm on this?
2. What is the significance of Version#1 and Version#2? Which one is used for what?
Thanks,
Kumar T.