From commits-return-650-apmail-knox-commits-archive=knox.apache.org@knox.apache.org Sat Apr 19 21:02:07 2014 Return-Path: X-Original-To: apmail-knox-commits-archive@minotaur.apache.org Delivered-To: apmail-knox-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 31D8510804 for ; Sat, 19 Apr 2014 21:02:07 +0000 (UTC) Received: (qmail 55564 invoked by uid 500); 19 Apr 2014 21:02:06 -0000 Delivered-To: apmail-knox-commits-archive@knox.apache.org Received: (qmail 55538 invoked by uid 500); 19 Apr 2014 21:02:06 -0000 Mailing-List: contact commits-help@knox.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@knox.apache.org Delivered-To: mailing list commits@knox.apache.org Received: (qmail 55531 invoked by uid 99); 19 Apr 2014 21:02:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 21:02:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 21:02:04 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 72BD3238890B; Sat, 19 Apr 2014 21:01:44 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1588706 - in /knox: site/books/knox-0-4-0/knox-0-4-0-new.html site/books/knox-0-4-0/knox-0-4-0.html trunk/books/0.4.0/quick_start.md Date: Sat, 19 Apr 2014 21:01:44 -0000 To: commits@knox.apache.org From: lmccay@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20140419210144.72BD3238890B@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: lmccay Date: Sat Apr 19 21:01:43 2014 New Revision: 1588706 URL: http://svn.apache.org/r1588706 Log: KNOX-322 qualified the specific file cleaned by gateway.sh clean Modified: knox/site/books/knox-0-4-0/knox-0-4-0-new.html knox/site/books/knox-0-4-0/knox-0-4-0.html knox/trunk/books/0.4.0/quick_start.md Modified: knox/site/books/knox-0-4-0/knox-0-4-0-new.html URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-4-0/knox-0-4-0-new.html?rev=1588706&r1=1588705&r2=1588706&view=diff ============================================================================== --- knox/site/books/knox-0-4-0/knox-0-4-0-new.html (original) +++ knox/site/books/knox-0-4-0/knox-0-4-0-new.html Sat Apr 19 21:01:43 2014 @@ -91,7 +91,7 @@

This will create a directory knox-{VERSION} in your current directory. The directory knox-{VERSION} will considered your {GATEWAY_HOME}

6 - Start LDAP embedded in Knox

Knox comes with an LDAP server for demonstration purposes.

cd {GATEWAY_HOME}
 bin/ldap.sh start
-

7 - Start Knox

The gateway can be started in one of two ways, as java -jar or with a shell script.

Starting via script

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.

linux
+

7 - Start Knox

The gateway can be started using the provided shell script.

Starting via script

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.

linux
cd {GATEWAY_HOME}
 bin/knoxcli.sh create-master

The cli will prompt you for the master secret (i.e. password).

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.

@@ -103,7 +103,7 @@ bin/gateway.sh stop

If for some reason the gateway is stopped other than by using the command above you may need to clear the tracking PID.

cd {GATEWAY_HOME}
 bin/gateway.sh clean
-

NOTE: This command will also clear any log output in /var/log/knox so use this with caution.

8 - Do Hadoop with Knox

Put a file in HDFS via Knox.

CAT a file in HDFS via Knox.

Invoke the LISTSTATUS operation on WebHDFS via the gateway.

This will return a directory listing of the root (i.e. /) directory of HDFS.

+

NOTE: This command will also clear any .out and .err file from the /var/log/knox directory so use this with caution.

8 - Do Hadoop with Knox

Put a file in HDFS via Knox.

CAT a file in HDFS via Knox.

Invoke the LISTSTATUS operation on WebHDFS via the gateway.

This will return a directory listing of the root (i.e. /) directory of HDFS.

curl -i -k -u guest:guest-password -X GET \
     'https://localhost:8443/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS'

The results of the above command should result in something to along the lines of the output below. The exact information returned is subject to the content within HDFS in your Hadoop cluster. Successfully executing this command at a minimum proves that the gateway is properly configured to provide access to WebHDFS. It does not necessarily provide that any of the other services are correct configured to be accessible. To validate that see the sections for the individual services in Service Details.

Modified: knox/site/books/knox-0-4-0/knox-0-4-0.html URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-4-0/knox-0-4-0.html?rev=1588706&r1=1588705&r2=1588706&view=diff ============================================================================== --- knox/site/books/knox-0-4-0/knox-0-4-0.html (original) +++ knox/site/books/knox-0-4-0/knox-0-4-0.html Sat Apr 19 21:01:43 2014 @@ -91,7 +91,7 @@

This will create a directory knox-{VERSION} in your current directory. The directory knox-{VERSION} will considered your {GATEWAY_HOME}

6 - Start LDAP embedded in Knox

Knox comes with an LDAP server for demonstration purposes.

cd {GATEWAY_HOME}
 bin/ldap.sh start
-

7 - Start Knox

The gateway can be started in one of two ways, as java -jar or with a shell script.

Starting via script

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.

linux
+

7 - Start Knox

The gateway can be started using the provided shell script.

Starting via script

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.

linux
cd {GATEWAY_HOME}
 bin/knoxcli.sh create-master

The cli will prompt you for the master secret (i.e. password).

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.

@@ -103,7 +103,7 @@ bin/gateway.sh stop

If for some reason the gateway is stopped other than by using the command above you may need to clear the tracking PID.

cd {GATEWAY_HOME}
 bin/gateway.sh clean
-

NOTE: This command will also clear any log output in /var/log/knox so use this with caution.

8 - Do Hadoop with Knox

Put a file in HDFS via Knox.

CAT a file in HDFS via Knox.

Invoke the LISTSTATUS operation on WebHDFS via the gateway.

This will return a directory listing of the root (i.e. /) directory of HDFS.

+

NOTE: This command will also clear any .out and .err file from the /var/log/knox directory so use this with caution.

8 - Do Hadoop with Knox

Put a file in HDFS via Knox.

CAT a file in HDFS via Knox.

Invoke the LISTSTATUS operation on WebHDFS via the gateway.

This will return a directory listing of the root (i.e. /) directory of HDFS.

curl -i -k -u guest:guest-password -X GET \
     'https://localhost:8443/gateway/sandbox/webhdfs/v1/?op=LISTSTATUS'

The results of the above command should result in something to along the lines of the output below. The exact information returned is subject to the content within HDFS in your Hadoop cluster. Successfully executing this command at a minimum proves that the gateway is properly configured to provide access to WebHDFS. It does not necessarily provide that any of the other services are correct configured to be accessible. To validate that see the sections for the individual services in Service Details.

Modified: knox/trunk/books/0.4.0/quick_start.md URL: http://svn.apache.org/viewvc/knox/trunk/books/0.4.0/quick_start.md?rev=1588706&r1=1588705&r2=1588706&view=diff ============================================================================== --- knox/trunk/books/0.4.0/quick_start.md (original) +++ knox/trunk/books/0.4.0/quick_start.md Sat Apr 19 21:01:43 2014 @@ -125,7 +125,7 @@ Knox comes with an LDAP server for demon ### 7 - Start Knox ### -The gateway can be started in one of two ways, as java -jar or with a shell script. +The gateway can be started using the provided shell script. ###### Starting via script @@ -157,7 +157,7 @@ If for some reason the gateway is stoppe cd {GATEWAY_HOME} bin/gateway.sh clean -__NOTE: This command will also clear any log output in /var/log/knox so use this with caution.__ +__NOTE: This command will also clear any .out and .err file from the /var/log/knox directory so use this with caution.__ ### 8 - Do Hadoop with Knox