GitHub user fsareshwala opened a pull request:
https://github.com/apache/bigtop/pull/84
BIGTOP-2293. Add puppet recipes for qfs components
This change adds puppet recipes to the bigtop source code for qfs
components:
qfs-metaserver, qfs-chunkserver, and qfs-client. The puppet recipes install
the
necessary packages, create necessary files and directories, generate
configuration with the correct ports and paths, and finally start the
services
so that they can talk to each other.
I have tested to make sure that the systems work properly by logging in
manually
to the docker container and interacting with the chunkserver and metaserver
using the qfs client. In my next commit, I will add testing to the bigtop
codebase so that we don't need to use manual inspection to ensure that
things
are working correctly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fsareshwala/bigtop qfs-puppet
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/84.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 #84
----
commit 72763415fffb58adfbf303cb1bac8e4f0a885da5
Author: Faraaz Sareshwala <[email protected]>
Date: 2016-02-02T22:19:27Z
BIGTOP-2293. Add puppet recipes for qfs components
This change adds puppet recipes to the bigtop source code for qfs
components:
qfs-metaserver, qfs-chunkserver, and qfs-client. The puppet recipes install
the
necessary packages, create necessary files and directories, generate
configuration with the correct ports and paths, and finally start the
services
so that they can talk to each other.
I have tested to make sure that the systems work properly by logging in
manually
to the docker container and interacting with the chunkserver and metaserver
using the qfs client. In my next commit, I will add testing to the bigtop
codebase so that we don't need to use manual inspection to ensure that
things
are working correctly.
----
---
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.
---
