… in progress. Please see README_CCF_v4.md for usage instructions

Signed-off-by: Ubuntu <ccf@prakash-services.ngrbedaihgkeramjr13nhjagoc.bx.internal.cloudapp.net>

…th what currently exists for v1.0.19

Signed-off-by: Ubuntu <ccf@prakash-services.ngrbedaihgkeramjr13nhjagoc.bx.internal.cloudapp.net>

In order to get the new CCF to run with the sandbox script
several changes needed to be made. Most importantly, the ledger
URL must be specified with an IP address, not a domain name.
Second, the docker build process is slightly changed to accommodate
the lack of a configuration step in the new build process. As part
of that update, the dependency on PDO_LEDGER_URL environment variable
for configuration is removed and the scripts for configuring the
CCF instance now take explicit host/port parameters. As part of the
update a lot of old unused code was removed from those scripts.

Right now the code assumes that the creation of the ledger keys
by the CCF node is a sufficient indicator that the node is ready.
Some additional checks are in the generate_ledger_authority script
which should be the first called after CCF is started. These
checks should be added to the other scripts as well.

Signed-off-by: Mic Bowman <mic.bowman@intel.com>

Added a new function for forcing name/address to an ip address. This
is useful since CCF requires ledger URLs and interfaces to be
specified as IP addresses.

Pushed changes to use the new function into the docker tools
and the script to start CCF.

Signed-off-by: Mic Bowman <mic.bowman@intel.com>

Fixed spelling issue, removed commented code, and
(only functional change) added one more check for
port availability before starting the CCF services.

Signed-off-by: Mic Bowman <mic.bowman@intel.com>