GitHub user kwmonroe opened a pull request:

    https://github.com/apache/bigtop/pull/155

    BIGTOP-2571: cwr driven updates to the zeppelin juju charm

    Simplify our smoke test (it's must simpler and faster to smoke 
zeppelin/spark than it is to smoke zeppelin/hadoop).
    
    Since zeppelin is based on hadoop-client, we were inheriting the client's 
01-basic-deployment.py test, which installs `hadoop-client`.  Zeppelin tests 
don't need hadoop client, so override this test with one that does a simple 
deployment of just the zeppelin charm.
    
    While we're in here, make the readme consistent with other bigtop charms 
and set our application version for `juju status` output.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/juju-solutions/bigtop bug/z-cwr-fixes

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/bigtop/pull/155.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 #155
    
----
commit 712f358ea949e267afdc6f6c8cf153dc9d2e6d00
Author: Kevin W Monroe <[email protected]>
Date:   2016-10-29T16:28:18Z

    simplify amulet test (zeppelin is standalone now); use new action syntax

commit 337d714218c812fa742d589c77d4f182a51a4e76
Author: Kevin W Monroe <[email protected]>
Date:   2016-10-29T18:40:08Z

    update readme to be consistent with other bigtop charms; make amulet test 
use a spark relation (otherwise zepp standalone defaults to yarn, which would 
require a whole hadooop env to test)

commit 434f080a143393f0dd1ad056191cd2a89b4e2d77
Author: Kevin W Monroe <[email protected]>
Date:   2016-11-04T19:41:46Z

    add basic deployment test in addition to smoke test; set app version for 
juju status

----


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

Reply via email to