GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/275
BIGTOP-2867: spark charm: make bigtop version configurable
See [BIGTOP-2867](https://issues.apache.org/jira/browse/BIGTOP-2867) for
details on the upgrade support provided by this PR.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/juju-solutions/bigtop
feature/BIGTOP-2867-spark-upgrade
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/275.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #275
----
commit c2197f2bf5c517f5e262300c85a40fb16a8a45b9
Author: Kevin W Monroe <[email protected]>
Date: 2017-08-03T14:56:24Z
BIGTOP-2867: spark charm: make bigtop version configurable
Allow the user to reinstall spark to pick up package changes when
the bigtop version changes.
LIB:
- do not trigger puppet if a reinstall is in progress
- misc comment cleanup
REACTIVE:
- driveby: more accurate status when waiting on yarn to become ready
- update status with reinstall option if available
- move config.changed to a new handler capable of forcing a reinstall
even if our topology hasnt changed
- new reconfig_spark handler handles all config-changed except repo version
changes
- new check_repo_version handler configures a site.yaml for the current
configured bigtop version
ACTIONS:
- new reinstall action
commit d28876daf45f44af56bd42becf059ce75d78d9e4
Author: Kevin W Monroe <[email protected]>
Date: 2017-08-07T18:19:37Z
tweak reinstall action with better failure messaging
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
