This Charm will assist Hadoop MapReduce application developers to focus on application development logic then spending long pain-full hours/days searching for appropriate hadoop packages, matching development tools, install/configure required packages, and finally build an isolate test/development platform.
This charm will seamlessly build a fully functional Hadoop 2.2.0 development environment on an isolated Ubuntu Linux Container or a remote cloud environment in under 5 minutes.
This charm will automate following required steps:
1) Install all Hadoop 2.x binary and source packages
2) Install the latest openjdk 7 jdk
3) Fully configure and setup an operational hadoop on a pseudo-distributed environment (i.e. ssh)
4) Configure a mapreduce build environment.
5) Install other useful development packages
maven, build-essential, autoconf, automake, libtool, cmak,e zlib1g-dev, pkg-config,
libssl-dev, and snappy packages
Hello Amir,
Thanks very much for your work on this hadoop2-devel charm! I recognize that there is a big hadoop community that need to deploy development environments fast and this charm does fill that need.
We had a discussion about renaming this charm since there is no charm named “hadoop2” currently available. Also the abbreviation “devel” is not widely used so I would suggest hadoop-development or hadoop-sdk or something else that reflects the charm. I have issues with the charm name but I have found other things in the review that I would also like to see fixed in future revisions.
The charm proof command had a Informational message that I have never seen before.
I: relation install has no hooks
I checked you metadata.yaml file defines a “install” relationship. As you know install is a hook name and can be considered reserved. I would recommend renaming the “install” relation to something else or removing the relation if there is no http interface.
config.yaml has a default boolean configuration option that is never used. Please remove the default (unused) configuration.
Empty hooks:
I know that charm proof reports Informational messages if start, stop, or config-changed hooks are not present but it is safe to remove them if you do not intend to use them. The upgrade-charm hook can be removed without an informational message from charm proof.
README.md:
The README looks good. I noticed some formatting problems.
Mistyped “cmak,e”
URL get resolved to “https:/
Formatting in Usage section is off. Indent Step #1
URL gets resolved to “https:/
Add bug location to the Contact Information section.
https:/
Perhaps adding some getting started information in the README would be good here. For instance where are the hadoop binaries on this deployed system? How would a developer know where to put their development files?
In the discussion we had about hadoop2-devel charm, we also talked about possibly putting this charm in your namespace rather than in the charm store. The benefit would be to not have dual maintenance between the normal hadoop charm and this charm. The drawback would be that the Juju user would have to install it from your own namespace. In the end we want to provide value to the Juju user, and not confuse them.
Another suggestion that came out of the discussion was to add a configuration value to use different versions of hadoop as a configuration option. This would be more flexible than the current hadoop charm.
Make it easy to publish map reduce applications to production. So if a developer is done with his/her map reduce program how can we make it easer to get on the “production” hadoop charm? Relation and run a script, or just run a script with the juju run command.
Build hadoop from source so we can build it on other pla...