knox-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lmc...@apache.org
Subject svn commit: r1581372 - in /knox/site/books/knox-incubating-0-4-0: knox-incubating-0-4-0-new.html knox-incubating-0-4-0.html
Date Tue, 25 Mar 2014 15:27:03 GMT
Author: lmccay
Date: Tue Mar 25 15:27:03 2014
New Revision: 1581372

URL: http://svn.apache.org/r1581372
Log:
site generated

Modified:
    knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0-new.html
    knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0.html

Modified: knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0-new.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0-new.html?rev=1581372&r1=1581371&r2=1581372&view=diff
==============================================================================
--- knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0-new.html (original)
+++ knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0-new.html Tue Mar 25 15:27:03
2014
@@ -99,22 +99,31 @@
 <pre><code>sudo rpm -ihv knox-incubating-{VERSION}.rpm
 </code></pre><h3><a id="6+-+Start+LDAP+embedded+in+Knox"></a>6
- Start LDAP embedded in Knox</h3><p>Knox comes with an LDAP server for demonstration
purposes.</p>
 <pre><code>cd {GATEWAY_HOME}
-java -jar bin/ldap.jar conf &amp;
-</code></pre><h3><a id="7+-+Start+Knox"></a>7 - Start Knox</h3><p>The
gateway can be started in one of two ways, as java -jar or with a shell script.</p><h6><a
id="Starting+via+Java"></a>Starting via Java</h6><p>This is the simplest
way to start the gateway. Starting this way will result in all logging being written directly
to standard output.</p>
+bin/ldap.sh start
+</code></pre><h3><a id="7+-+Start+Knox"></a>7 - Start Knox</h3><p>The
gateway can be started in one of two ways, as java -jar or with a shell script.</p><h6><a
id="Starting+via+script"></a>Starting via script</h6><p>Run the knoxcli
create-master command in order to persist the master secret that is used to protect the key
and credential stores for the gateway instance.</p><h6><a id="linux"></a>linux</h6>
 <pre><code>cd {GATEWAY_HOME}
-java -jar bin/gateway.jar
-</code></pre><p>Upon start, Knox server will prompt you for the master
secret (i.e. password). This secret is used to secure artifacts used by the gateway server
for things like SSL and credential/password aliasing. This secret will have to be entered
at startup unless you choose to persist it.</p><h6><a id="Starting+via+script+(*nix+only)"></a>Starting
via script (*nix only)</h6><p>Run the setup command with root privileges.</p>
+bin/knoxcli.sh create-master
+</code></pre><h5><a id="windows"></a>windows</h5>
 <pre><code>cd {GATEWAY_HOME}
-sudo bin/gateway.sh setup
-</code></pre><p>The server will prompt you for the master secret (i.e.
password).</p><p>The server can then be started without root privileges using
this command.</p>
+bin\knoxcli.cmd create-master
+</code></pre><p>The cli will prompt you for the master secret (i.e. password).</p><p>The
server will discover the persisted master secret during start up and complete the setup process
for demo installs. A demo install will consist of a knox gateway instance with an identity
certificate for localhost. This will require clients to be on the same machine or to turn
off hostname verification. For more involved deployments, See the Knox CLI section of this
document for additional commands - incuding the ability to create a self-signed certificate
for a specific hostname.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh start
-</code></pre><p>When starting the gateway this way the process will be
run in the backgroud. The log output is written into the directory /var/log/knox. In addition
a PID (process ID) is written into /var/run/knox.</p><p>In order to stop a gateway
that was started with the script use this command.</p>
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd start
+</code></pre><p>When starting the gateway this way the process will be
run in the backgroud. The log output is written into the directory /var/log/knox. In addition
a PID (process ID) is written into /var/run/knox.</p><p>In order to stop a gateway
that was started with the script use this command.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh stop
-</code></pre><p>If for some reason the gateway is stopped other than by
using the command above you may need to clear the tracking PID.</p>
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd start
+</code></pre><p>If for some reason the gateway is stopped other than by
using the command above you may need to clear the tracking PID.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh clean
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd clean
 </code></pre><p><strong>NOTE: This command will also clear any log
output in /var/log/knox so use this with caution.</strong></p><h3><a
id="8+-+Do+Hadoop+with+Knox"></a>8 - Do Hadoop with Knox</h3><h4><a
id="Put+a+file+in+HDFS+via+Knox."></a>Put a file in HDFS via Knox.</h4><h4><a
id="CAT+a+file+in+HDFS+via+Knox."></a>CAT a file in HDFS via Knox.</h4><h4><a
id="Invoke+the+LISTSATUS+operation+on+WebHDFS+via+the+gateway."></a>Invoke the LISTSATUS
operation on WebHDFS via the gateway.</h4><p>This will return a directory listing
of the root (i.e. /) directory of HDFS.</p>
 <pre><code>curl -i -k -u guest:guest-password -X GET \
     &#39;https://localhost:8443/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS&#39;

Modified: knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0.html?rev=1581372&r1=1581371&r2=1581372&view=diff
==============================================================================
--- knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0.html (original)
+++ knox/site/books/knox-incubating-0-4-0/knox-incubating-0-4-0.html Tue Mar 25 15:27:03 2014
@@ -99,22 +99,31 @@
 <pre><code>sudo rpm -ihv knox-incubating-{VERSION}.rpm
 </code></pre><h3><a id="6+-+Start+LDAP+embedded+in+Knox"></a>6
- Start LDAP embedded in Knox</h3><p>Knox comes with an LDAP server for demonstration
purposes.</p>
 <pre><code>cd {GATEWAY_HOME}
-java -jar bin/ldap.jar conf &amp;
-</code></pre><h3><a id="7+-+Start+Knox"></a>7 - Start Knox</h3><p>The
gateway can be started in one of two ways, as java -jar or with a shell script.</p><h6><a
id="Starting+via+Java"></a>Starting via Java</h6><p>This is the simplest
way to start the gateway. Starting this way will result in all logging being written directly
to standard output.</p>
+bin/ldap.sh start
+</code></pre><h3><a id="7+-+Start+Knox"></a>7 - Start Knox</h3><p>The
gateway can be started in one of two ways, as java -jar or with a shell script.</p><h6><a
id="Starting+via+script"></a>Starting via script</h6><p>Run the knoxcli
create-master command in order to persist the master secret that is used to protect the key
and credential stores for the gateway instance.</p><h6><a id="linux"></a>linux</h6>
 <pre><code>cd {GATEWAY_HOME}
-java -jar bin/gateway.jar
-</code></pre><p>Upon start, Knox server will prompt you for the master
secret (i.e. password). This secret is used to secure artifacts used by the gateway server
for things like SSL and credential/password aliasing. This secret will have to be entered
at startup unless you choose to persist it.</p><h6><a id="Starting+via+script+(*nix+only)"></a>Starting
via script (*nix only)</h6><p>Run the setup command with root privileges.</p>
+bin/knoxcli.sh create-master
+</code></pre><h5><a id="windows"></a>windows</h5>
 <pre><code>cd {GATEWAY_HOME}
-sudo bin/gateway.sh setup
-</code></pre><p>The server will prompt you for the master secret (i.e.
password).</p><p>The server can then be started without root privileges using
this command.</p>
+bin\knoxcli.cmd create-master
+</code></pre><p>The cli will prompt you for the master secret (i.e. password).</p><p>The
server will discover the persisted master secret during start up and complete the setup process
for demo installs. A demo install will consist of a knox gateway instance with an identity
certificate for localhost. This will require clients to be on the same machine or to turn
off hostname verification. For more involved deployments, See the Knox CLI section of this
document for additional commands - incuding the ability to create a self-signed certificate
for a specific hostname.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh start
-</code></pre><p>When starting the gateway this way the process will be
run in the backgroud. The log output is written into the directory /var/log/knox. In addition
a PID (process ID) is written into /var/run/knox.</p><p>In order to stop a gateway
that was started with the script use this command.</p>
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd start
+</code></pre><p>When starting the gateway this way the process will be
run in the backgroud. The log output is written into the directory /var/log/knox. In addition
a PID (process ID) is written into /var/run/knox.</p><p>In order to stop a gateway
that was started with the script use this command.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh stop
-</code></pre><p>If for some reason the gateway is stopped other than by
using the command above you may need to clear the tracking PID.</p>
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd start
+</code></pre><p>If for some reason the gateway is stopped other than by
using the command above you may need to clear the tracking PID.</p><h5><a id="linux"></a>linux</h5>
 <pre><code>cd {GATEWAY_HOME}
 bin/gateway.sh clean
+</code></pre><h5><a id="windows"></a>windows</h5>
+<pre><code>cd {GATEWAY_HOME}
+bin\gateway.cmd clean
 </code></pre><p><strong>NOTE: This command will also clear any log
output in /var/log/knox so use this with caution.</strong></p><h3><a
id="8+-+Do+Hadoop+with+Knox"></a>8 - Do Hadoop with Knox</h3><h4><a
id="Put+a+file+in+HDFS+via+Knox."></a>Put a file in HDFS via Knox.</h4><h4><a
id="CAT+a+file+in+HDFS+via+Knox."></a>CAT a file in HDFS via Knox.</h4><h4><a
id="Invoke+the+LISTSATUS+operation+on+WebHDFS+via+the+gateway."></a>Invoke the LISTSATUS
operation on WebHDFS via the gateway.</h4><p>This will return a directory listing
of the root (i.e. /) directory of HDFS.</p>
 <pre><code>curl -i -k -u guest:guest-password -X GET \
     &#39;https://localhost:8443/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS&#39;



Mime
View raw message