You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kevin W Monroe (JIRA)" <ji...@apache.org> on 2017/08/28 21:45:01 UTC
[jira] [Resolved] (BIGTOP-2867) spark charm: make bigtop version
configurable
[ https://issues.apache.org/jira/browse/BIGTOP-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin W Monroe resolved BIGTOP-2867.
------------------------------------
Resolution: Fixed
Rev 55 of the spark charm contains this fix:
https://jujucharms.com/spark/55
Results look good for cloud/local tests:
http://bigtop.charm.qa/cwr_bundle_spark_processing/89/report.html
> spark charm: make bigtop version configurable
> ---------------------------------------------
>
> Key: BIGTOP-2867
> URL: https://issues.apache.org/jira/browse/BIGTOP-2867
> Project: Bigtop
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.2.0
> Reporter: Kevin W Monroe
> Assignee: Kevin W Monroe
> Fix For: 1.3.0
>
>
> We've landed support for allowing users to change the bigtop version at runtime. Each charm will need to handle any application-specific config required during a package upgrade. This jira covers version support for the spark charm.
> The workflow looks like this:
> # deploy spark with default repo (bigtop-1.2.0)
> - juju deploy spark
> # request a change to bigtop-1.2.1
> - juju config spark bigtop_version=1.2.1
> # user is notified that a spark upgrade is available and should run 'reinstall'
> - juju run-action spark/0 reinstall
> # puppet apply completes and charm status is updated with new version info
> - juju status
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)