bigcy / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

Document the procedure needed to upgrade from a tungsten-installer deployment to tpm. #669

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
1. To which tool/application/daemon will this feature apply?

installer scripts

2. Describe the feature in general

Document the steps needed to upgrade from a tungsten-installer deployment to a 
new version using tpm

3. Describe the feature interface

* a documentation page
* eventually, a cookbook script

4. Give an idea (if applicable) of a possible implementation

see above

5. Describe pros and cons of this feature.

5a. Why the world will be a better place with this feature.

Users need to move on from earlier installers, if they want to use the newer 
features, such as security.

5b. What hardship will the human race have to endure if this feature is
implemented.

upgrades between different versions of an installer are always troublesome.

6. Notes

Original issue reported on code.google.com by g.maxia on 12 Aug 2013 at 12:26

GoogleCodeExporter commented 9 years ago
The upgrade process is straightforward and works the same as an update within 
versions using tpm. This has been noted and and updated in the documentation, 
currently published in the wiki here: 

https://docs.continuent.com/wiki/display/TEDOC/Upgrading+Tungsten+Replicator

Original comment by mc.br...@continuent.com on 19 Aug 2013 at 9:37