[GitHub] bigtop pull request #148: BIGTOP-2548: Refresh charms for Juju 2.0 and Xenia...

2016-10-12 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] bigtop pull request #148: BIGTOP-2548: Refresh charms for Juju 2.0 and Xenia...

2016-10-07 Thread kwmonroe
GitHub user kwmonroe opened a pull request:

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

BIGTOP-2548: Refresh charms for Juju 2.0 and Xenial

- update layer repo to upstream bigtop location
- update metadata to inherit tags defined in bigtop base layer
- update charm tests to use xenial base OS
- alter plugin to correctly make java relation optional
- use layer options to override NN and RM ports in puppet recipes
- run bigtop smoke tests for RM (yarn) and Slave (hdfs + mapreduce)
- run simple smoke tests for NN and plugin:
  - plugin lacks venv modules required to instantiate the Bigtop class, so 
it cannot call Bigtop.run_smoke_tests.
  - NN cannot successfully run the 'hdfs' smoke test. It fails on the 
distcp test, presumably because it lacks a component like the DN.
- readme updates for consistent messaging and 2.0 instructions

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

$ git pull https://github.com/juju-solutions/bigtop 
bug/BIGTOP-2548/xenial-charm-refresh

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

https://github.com/apache/bigtop/pull/148.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 #148






---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---