GitHub user fsareshwala opened a pull request:
https://github.com/apache/bigtop/pull/83
BIGTOP-2285. add qfs rpm and debian packaging code
This change adds code to bigtop to package qfs for debian and rpm systems.
The
packages produced are specific to their functions, e.g. a separate package
for
the metaserver, chunkserver, webui, client tools, development headers and
libraries, etc. This way, users can select which packages they wish to
install
on which system in their infrastructure. One caveat worth mentioning is
that the
packages themselves don't contain configuration files for the services in
question. The configuration files are provided by the puppet deploy scripts
that
come with the bigtop repository. Those will be submitted in a separate
change.
In order to build qfs and its respective packages, various dependencies were
added to the toolchain puppet tasks (e.g. boost-devel). These will be
installed
along with the other dependencies that get installed during the toolchain
gradle
task. In doing so, users should be presented with a seamless setup process
to
get qfs packages building.
I have tested to make sure that packaging is correct by using the qfs-rpm
and
qfs-deb grandle tasks to generate the respective rpm and debian packages. I
then
manually inspected package contents to ensure that files were being
installed
into the correct location.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fsareshwala/bigtop qfs-packaging
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/83.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 #83
----
commit c5f45c8f4b6e43e06f439a0cdb89844be65571fc
Author: Faraaz Sareshwala <[email protected]>
Date: 2016-01-13T23:29:46Z
BIGTOP-2285. add qfs rpm and debian packaging code
This change adds code to bigtop to package qfs for debian and rpm systems.
The
packages produced are specific to their functions, e.g. a separate package
for
the metaserver, chunkserver, webui, client tools, development headers and
libraries, etc. This way, users can select which packages they wish to
install
on which system in their infrastructure. One caveat worth mentioning is
that the
packages themselves don't contain configuration files for the services in
question. The configuration files are provided by the puppet deploy scripts
that
come with the bigtop repository. Those will be submitted in a separate
change.
In order to build qfs and its respective packages, various dependencies were
added to the toolchain puppet tasks (e.g. boost-devel). These will be
installed
along with the other dependencies that get installed during the toolchain
gradle
task. In doing so, users should be presented with a seamless setup process
to
get qfs packages building.
I have tested to make sure that packaging is correct by using the qfs-rpm
and
qfs-deb grandle tasks to generate the respective rpm and debian packages. I
then
manually inspected package contents to ensure that files were being
installed
into the correct location.
----
---
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.
---
