Closed gordyt closed 7 years ago
@fatkudu - Should I pull the ephemeral references out of the upgrade guide and submit them in a separate PR to a "zms-dev" branch? Is simple to do.
Yes please @gordyt. I'd like for us to have a baseline of documentation that makes sense for 8.7
@fatkudu OK, the PR is updated to exclude the ephemeral stuff. Once this has been approved and merged into master, I'll submit separate (small) PR for the ephemeral additions.
The table of contents is less detailed than the original. Consider :toclevels: 3
?
I'd also be tempted to be sparing in the use of ZCS aka {product-abbrev}. I think we should either use Zimbra Collaboration of ZCS pretty much everywhere and not chop and change between the 2.
as user zimbra: zimbra$ crontab -l | grep -i cert
0 0 1 /opt/zimbra/libexec/zmcheckexpiredcerts -days 30 -email
Added two new files to the
installguides
repo:upgrade.adoc
- The main documentupgrade-process-inc.adoc
- Included byupgrade.adoc
Updated the
README.adoc
to add instructions for building.I started by porting the old upgrade instructions to asciidoc format, cleaning up things in the process. Then added in instructions related to migrating emphemeral storage backends.
In the process I noted a few items (from original documentation) that made references to other documentation that I could not find. These are all marked with "TODO -....". Would appreciate any feedback as to where I might find that documentation so that it may be referenced properly.
Another thing related to supported OS versions. How far back are we still supporting Ubuntu? All the way back to 12.04? If not, I'll remove those references.
NOTE: Added two additional commits:
2017-02-21, 09:42 - Removed ephemeral data section from this PR. Will create a
zms-dev
branch and submit that section separately to the new branch. Ultimately we will tag themaster
branch for 8.7, merge thezms-dev
branch intomaster
, and tag that for 8.8.2017-02-24, 09:53
rdd
files produced byzmlogger
.ZMS-435
that incorporates the latest updates.