-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial import of very brief usage instructions
- Loading branch information
1 parent
e26450b
commit 7d2e9fb
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,23 @@ | ||
# weka_upgrade_checker | ||
Weka Upgrade Checker | ||
|
||
The script takes into account all of the best practices requirements outlined in the document for upgrade best practices. | ||
|
||
It is recommended that the pre-upgrade checker be run 24hrs in advance so that all issues can be resolved prior to the planned upgrade window. | ||
|
||
|
||
## Prior to running the script follow the prerequisites listed below: | ||
|
||
1. The script should be run on a backend weka host | ||
2. You should have either sudo access or be root. On AWS systems it's usually easier to be ec2-user | ||
3. Your user should be logged to WEKA, such that `weka status` etc work | ||
4. Passwordless SSH should be configured prior to starting. | ||
|
||
[Github link](https://github.com/weka/tools/tree/master/weka_upgrade_checker) | ||
|
||
To download directly to a host with Internet access (into current directory), make the script executable, and show syntax help: | ||
|
||
```bash | ||
curl -LO https://github.com/weka/tools/raw/master/weka_upgrade_checker/weka_upgrade_checker.py | ||
python3.8 ./weka_upgrade_checker.py | ||
``` |