-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add update instructions for RPM/DEB and bin distribution #212
Conversation
I added the links for the DEB package on the download pages. This is subject to our ability of building the DEB and RPM packages for snapshot though /cc @richardcloudsoft |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good; I tested the upgrade from 0.11.0 to 0.12.0-rc3 on centos7 (installing the rpm, starting 0.11.0, deploying a simple app, then following these upgrade instructions).
Other than these comments, the instructions worked great for me.
Thanks @tbouron!
guide/ops/upgrade.md
Outdated
|
||
3. Confirm that Brooklyn is definitely not running (see step 1 above). | ||
|
||
4. Delete the Brooklyn install directory: `sudo rm -r /opt/brooklyn`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also need to sudo rm -r /var/log/brooklyn/
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, will amend
guide/ops/upgrade.md
Outdated
# Ubuntu / Debian | ||
sudo dpkg -i apache-brooklyn-xxxx.all.deb | ||
|
||
3. Wait for Brooklyn to be fully started (i.e. its web-console to be responsive). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me, brooklyn process wasn't running. Do you definitely expect it to auto-start on rpm install?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brooklyn does not start automatically, I should remove this step. Thanks @aledsage
guide/ops/upgrade.md
Outdated
|
||
7. Validate that the new release works, by starting in "HOT_BACKUP" mode. | ||
|
||
1. Before starting Brooklyn, reconfigure `./etc/org.apache.brooklyn.osgilauncher.cfg` and set `highAvailabilityMode=HOT_BACKUP`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be /etc/brooklyn/...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, will amend
guide/ops/upgrade.md
Outdated
# Ubuntu / Debian | ||
start brooklyn | ||
|
||
3. Check whether you have rebind ERROR messages in `./log/brooklyn.info.log`, e.g. `sudo grep -E "WARN|ERROR" /opt/brooklyn/log/brooklyn.debug.log`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd say "ERROR mesages in the brooklyn log, e.g. ..." (rather than the ./log/...
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd use sudo grep -E "Rebind|WARN|ERROR" /var/log/brooklyn/brooklyn.info.log
(important to include something like "Rebind" so the user sees a message about success, as well as some benign (?) warnings).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense @aledsage, will update
@aledsage Comments addressed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tbouron
This requires the
paths.html
page available with #210