diff options
Diffstat (limited to 'bigtop-deploy/juju/hadoop-processing')
| -rw-r--r-- | bigtop-deploy/juju/hadoop-processing/README.md | 45 | ||||
| -rw-r--r-- | bigtop-deploy/juju/hadoop-processing/bundle.yaml | 8 |
2 files changed, 23 insertions, 30 deletions
diff --git a/bigtop-deploy/juju/hadoop-processing/README.md b/bigtop-deploy/juju/hadoop-processing/README.md index 896a7936..9ad44b6a 100644 --- a/bigtop-deploy/juju/hadoop-processing/README.md +++ b/bigtop-deploy/juju/hadoop-processing/README.md @@ -38,10 +38,10 @@ and syslog activity. The applications that comprise this bundle are spread across 5 machines as follows: - * NameNode (HDFS) - * ResourceManager (YARN) + * NameNode v2.7.3 + * ResourceManager v2.7.3 * Colocated on the NameNode unit - * Slave (DataNode and NodeManager) + * Slave (DataNode and NodeManager) v2.7.3 * 3 separate units * Client (Hadoop endpoint) * Plugin (Facilitates communication with the Hadoop cluster) @@ -57,9 +57,8 @@ demands. # Deploying -A working Juju installation is assumed to be present. If Juju is not yet set -up, please follow the [getting-started][] instructions prior to deploying this -bundle. +This charm requires Juju 2.0 or greater. If Juju is not yet set up, please +follow the [getting-started][] instructions prior to deploying this bundle. > **Note**: This bundle requires hardware resources that may exceed limits of Free-tier or Trial accounts on some clouds. To deploy to these @@ -70,18 +69,10 @@ Deploy this bundle from the Juju charm store with the `juju deploy` command: juju deploy hadoop-processing -> **Note**: The above assumes Juju 2.0 or greater. If using an earlier version -of Juju, use [juju-quickstart][] with the following syntax: `juju quickstart -hadoop-processing`. - Alternatively, deploy a locally modified `bundle.yaml` with: juju deploy /path/to/bundle.yaml -> **Note**: The above assumes Juju 2.0 or greater. If using an earlier version -of Juju, use [juju-quickstart][] with the following syntax: `juju quickstart -/path/to/bundle.yaml`. - The charms in this bundle can also be built from their source layers in the [Bigtop charm repository][]. See the [Bigtop charm README][] for instructions on building and deploying these charms locally. @@ -93,7 +84,6 @@ mirror options. See [Configuring Models][] for more information. [getting-started]: https://jujucharms.com/docs/stable/getting-started [bundle.yaml]: https://github.com/apache/bigtop/blob/master/bigtop-deploy/juju/hadoop-processing/bundle.yaml -[juju-quickstart]: https://launchpad.net/juju-quickstart [Bigtop charm repository]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/charm [Bigtop charm README]: https://github.com/apache/bigtop/blob/master/bigtop-packages/src/charm/README.md [Configuring Models]: https://jujucharms.com/docs/stable/models-config @@ -127,25 +117,16 @@ Run the smoke-test actions as follows: juju run-action resourcemanager/0 smoke-test juju run-action slave/0 smoke-test -> **Note**: The above assumes Juju 2.0 or greater. If using an earlier version -of Juju, the syntax is `juju action do <application>/0 smoke-test`. - Watch the progress of the smoke test actions with: watch -n 2 juju show-action-status -> **Note**: The above assumes Juju 2.0 or greater. If using an earlier version -of Juju, the syntax is `juju action status`. - Eventually, all of the actions should settle to `status: completed`. If any report `status: failed`, that application is not working as expected. Get more information about a specific smoke test with: juju show-action-output <action-id> -> **Note**: The above assumes Juju 2.0 or greater. If using an earlier version -of Juju, the syntax is `juju action fetch <action-id>`. - ## Utilities Applications in this bundle include Hadoop command line and web utilities that can be used to verify information about the cluster. @@ -270,6 +251,18 @@ Multiple units may be added at once. For example, add four more slave units: juju add-unit -n4 slave +# Issues + +Apache Bigtop tracks issues using JIRA (Apache account required). File an +issue for this bundle at: + +https://issues.apache.org/jira/secure/CreateIssue!default.jspa + +Ensure `Bigtop` is selected as the project. Typically, bundle issues are filed +in the `deployment` component with the latest stable release selected as the +affected version. Any uncertain fields may be left blank. + + # Contact Information - <bigdata@lists.ubuntu.com> @@ -280,6 +273,6 @@ Multiple units may be added at once. For example, add four more slave units: - [Apache Bigtop home page](http://bigtop.apache.org/) - [Apache Bigtop issue tracking](http://bigtop.apache.org/issue-tracking.html) - [Apache Bigtop mailing lists](http://bigtop.apache.org/mail-lists.html) -- [Juju Bigtop charms](https://jujucharms.com/q/apache/bigtop) +- [Juju Big Data](https://jujucharms.com/big-data) +- [Juju Bigtop charms](https://jujucharms.com/q/bigtop) - [Juju mailing list](https://lists.ubuntu.com/mailman/listinfo/juju) -- [Juju community](https://jujucharms.com/community) diff --git a/bigtop-deploy/juju/hadoop-processing/bundle.yaml b/bigtop-deploy/juju/hadoop-processing/bundle.yaml index c4d8005e..ef5195ae 100644 --- a/bigtop-deploy/juju/hadoop-processing/bundle.yaml +++ b/bigtop-deploy/juju/hadoop-processing/bundle.yaml @@ -1,6 +1,6 @@ services: namenode: - charm: "cs:xenial/hadoop-namenode-13" + charm: "cs:xenial/hadoop-namenode-14" constraints: "mem=7G root-disk=32G" num_units: 1 annotations: @@ -9,7 +9,7 @@ services: to: - "0" resourcemanager: - charm: "cs:xenial/hadoop-resourcemanager-14" + charm: "cs:xenial/hadoop-resourcemanager-16" constraints: "mem=7G root-disk=32G" num_units: 1 annotations: @@ -18,7 +18,7 @@ services: to: - "0" slave: - charm: "cs:xenial/hadoop-slave-13" + charm: "cs:xenial/hadoop-slave-15" constraints: "mem=7G root-disk=32G" num_units: 3 annotations: @@ -29,7 +29,7 @@ services: - "2" - "3" plugin: - charm: "cs:xenial/hadoop-plugin-13" + charm: "cs:xenial/hadoop-plugin-14" annotations: gui-x: "1000" gui-y: "400" |