You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/07 18:23:01 UTC

[jira] [Commented] (BIGTOP-2867) spark charm: make bigtop version configurable

    [ https://issues.apache.org/jira/browse/BIGTOP-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116984#comment-16116984 ] 

ASF GitHub Bot commented on BIGTOP-2867:
----------------------------------------

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 <ke...@canonical.com>
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 <ke...@canonical.com>
Date:   2017-08-07T18:19:37Z

    tweak reinstall action with better failure messaging

----


> 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)