Based on the initial review the following modifications are made:

1) replaced /tmp with /var/lib/juju/hpcc which is created during install hook
   We do not use $CHARM_DIR since we want this directory to have the same name for all nodes.
   We cannot find variable $CHARM_ROOT. If there is a variable to point to /var/lib/juju we will
   be happy to use it instead of the hard-coded /var/lib/juju.

2) hpcc relation hook. For the first release there are no other charms related to hpcc. But
   in near future we will add other related charms, for example, ganglia-monitor and hadoop
   support, etc. We add an empty hpcc-relation-changed hook to satisfy the 'juju charm proof'

3) There is a potential security risk by using supplied ssh-key. For local deployment
   we added a sentence to recommend users to generate their own keys and replace the ones in
   hpcc/ssh-keys directory.  For deploy directly from juju-store we don't know how to use
   users' generated keys.

4) Regarding the README section on help scripts under hpcc/bin:
   Users would need to download the charm to use the scripts.
   There are two main shell scripts. These are now explained in the readme (see below).
   The other two python scripts are support scripts and users do not call them directly.

   config_hpcc.sh : When you use the `juju add-unit` command to add nodes, scripts are called
   automatically to provide a default configuration. If you want to configure manually, set
   auto-gen to 0, wait for all nodes to be in a "started" state, then call the config_hpcc.sh
   script using the following parameters:

     ./config_hpcc.sh -thornodes <# of thor nodes> -roxienodes <# of roxie nodes> -supportnodes
            <# of support nodes> -slavespernode <#of thor slaves per node>

   Another useful script reports the URL for the ECL Watch node. Call the get-url.sh script
   to display the cluster configuration and the URL for the ECL Watch service.

5) We updated the icon.svg file with our company logo