Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E397D200C16 for ; Thu, 9 Feb 2017 21:38:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E1ED7160B6E; Thu, 9 Feb 2017 20:38:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 90B2C160B4B for ; Thu, 9 Feb 2017 21:38:43 +0100 (CET) Received: (qmail 12733 invoked by uid 500); 9 Feb 2017 20:38:42 -0000 Mailing-List: contact commits-help@predictionio.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@predictionio.incubator.apache.org Delivered-To: mailing list commits@predictionio.incubator.apache.org Received: (qmail 12723 invoked by uid 99); 9 Feb 2017 20:38:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 20:38:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 29EE81A050D for ; Thu, 9 Feb 2017 20:38:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.218 X-Spam-Level: X-Spam-Status: No, score=-6.218 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id pAD9YY8Dl-EW for ; Thu, 9 Feb 2017 20:38:21 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 9D2ED5FE5F for ; Thu, 9 Feb 2017 20:38:06 +0000 (UTC) Received: (qmail 7856 invoked by uid 99); 9 Feb 2017 20:38:05 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 20:38:05 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 88786E04D6; Thu, 9 Feb 2017 20:38:05 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: git-site-role@apache.org To: commits@predictionio.incubator.apache.org Date: Thu, 09 Feb 2017 20:38:34 -0000 Message-Id: <6c05fe3513cc40fe92aa884ea8622828@git.apache.org> In-Reply-To: <380eeff7f4314472ad38f834be59ac53@git.apache.org> References: <380eeff7f4314472ad38f834be59ac53@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [31/51] [abbrv] [partial] incubator-predictionio-site git commit: Clean up before apache/incubator-predictionio#d674b89c7c3a17437bd406a497a08773c24c8007 archived-at: Thu, 09 Feb 2017 20:38:46 -0000 http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/install-sourcecode/index.html ---------------------------------------------------------------------- diff --git a/install/install-sourcecode/index.html b/install/install-sourcecode/index.html deleted file mode 100644 index 67ae5cb..0000000 --- a/install/install-sourcecode/index.html +++ /dev/null @@ -1,86 +0,0 @@ -Installing Apache PredictionIO (incubating) from Source Code
On this page
Edit this page

Assuming you are following the directory structure in the followoing, replace /home/abc with your own home directory wherever you see it.

Downloading Source Code

Download Apache PredictionIO (incubating) 0.10.0-incubating from an Apache mirror.

Building

Run the following at the directory where you downloaded the source code to build Apache PredictionIO (incubating).

1
-2
-3
$ tar zxvf apache-predictionio-0.10.0-incubating.tar.gz
-$ cd apache-predictionio-0.10.0-incubating
-$ ./make-distribution.sh
-

You should see something like the following when it finishes building successfully.

1
-2
-3
-4
-5
...
-PredictionIO-0.10.0-incubating/sbt/sbt
-PredictionIO-0.10.0-incubating/conf/
-PredictionIO-0.10.0-incubating/conf/pio-env.sh
-PredictionIO binary distribution created at PredictionIO-0.10.0-incubating.tar.gz
-

Extract the binary distribution you have just built.

1
$ tar zxvf PredictionIO-0.10.0-incubating.tar.gz
-

Installing Dependencies

Let us install dependencies inside a subdirectory of the Apache PredictionIO (incubating) installation. By following this convention, you can use Apache PredictionIO (incubating)'s default configuration as is.

1
$ mkdir PredictionIO-0.10.0-incubating/vendors
-

Spark Setup

Apache Spark is the default processing engine for PredictionIO. Download and extract it.

1
-2
$ wget http://d3kbcqa49mib13.cloudfront.net/spark-1.5.1-bin-hadoop2.6.tgz
-$ tar zxvfC spark-1.5.1-bin-hadoop2.6.tgz PredictionIO-0.10.0-incubating/vendors
-

If you decide to install Apache Spark to another location, you must edit PredictionIO-0.10.0-incubating/conf/pio-env.sh and change the SPARK_HOME variable to point to your own Apache Spark installation.

Storage Setup

PostgreSQL Setup

Setting up PostgreSQL to work with PredictionIO.

Make sure you have PostgreSQL installed. For Mac Users, Homebrew is recommended and can be used as

1
$ brew install postgresql
-

or on Ubuntu: apt-get install postgresql-9.4

Now that PostgreSQL is installed use the following comands

1
$ createdb pio
-

If you get an error of the form could not connect to server: No such file or directory, then you must first start the server manually,:

1
$ pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start
-

Finally use the command:

1
$ psql -c "create user pio with password 'pio'"
-

Your configuration in pio-env.sh is now compatible to run with PostgreSQL.

HBase and Elasticsearch Setup

Elasticsearch Setup

You may skip this section if you are using PostgreSQL or MySQL.

Elasticsearch is the default metadata store for PredictionIO. Download and extract it.

1
-2
$ wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.4.4.tar.gz
-$ tar zxvfC elasticsearch-1.4.4.tar.gz PredictionIO-0.10.0-incubating/vendors
-

If you decide to install Elasticsearch to another location, you must edit PredictionIO-0.10.0-incubating/conf/pio-env.sh and change the PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME variable to point to your own Elasticsearch installation.

If you are using a shared network, change the network.host line in PredictionIO-0.10.0-incubating/vendors/elasticsearch-1.4.4/config/elasticsearch.yml to network.host: 127.0.0.1 because by default, Elasticsearch looks for other machines on the network upon setup and you may run into weird errors if there are other machines that is also running Elasticsearch.

If you are not using the default setting at localhost, you may change the following in PredictionIO-0.10.0-incubating/conf/pio-env.sh to fit your setup.

1
-2
-3
PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch
-PIO_STORAGE_SOURCES_ELASTICSEARCH_HOSTS=localhost
-PIO_STORAGE_SOURCES_ELASTICSEARCH_PORTS=9300
-
HBase Setup

You may skip this section if you are using PostgreSQL or MySQL.

HBase is the default event data store for PredictionIO. Download and extract it.

1
-2
$ wget http://archive.apache.org/dist/hbase/hbase-1.0.0/hbase-1.0.0-bin.tar.gz
-$ tar zxvfC hbase-1.0.0-bin.tar.gz PredictionIO-0.10.0-incubating/vendors
-

If you decide to install HBase to another location, you must edit PredictionIO-0.10.0-incubating/conf/pio-env.sh and change the PIO_STORAGE_SOURCES_HBASE_HOME variable to point to your own HBase installation.

You will need to at least add a minimal configuration to HBase to start it in standalone mode. Details can be found here. Here, we are showing a sample minimal configuration.

For production deployment, run a fully distributed HBase configuration.

Edit PredictionIO-0.10.0-incubating/vendors/hbase-1.0.0/conf/hbase-site.xml.

1
-2
-3
-4
-5
-6
-7
-8
-9
-10
<configuration>
-  <property>
-    <name>hbase.rootdir</name>
-    <value>file:///home/abc/PredictionIO-0.10.0-incubating/vendors/hbase-1.0.0/data</value>
-  </property>
-  <property>
-    <name>hbase.zookeeper.property.dataDir</name>
-    <value>/home/abc/PredictionIO-0.10.0-incubating/vendors/hbase-1.0.0/zookeeper</value>
-  </property>
-</configuration>
-

HBase will create hbase.rootdir automatically to store its data.

Edit PredictionIO-0.10.0-incubating/vendors/hbase-1.0.0/conf/hbase-env.sh to set JAVA_HOME for the cluster. For example:

1
export JAVA_HOME=/usr/lib/jvm/java-8-oracle/jre
-

For Mac users, use this instead (change 1.8 to 1.7 if you have Java 7 installed):

1
export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
-

In addition, you must set your environment variable JAVA_HOME. For example, in /home/abc/.bashrc add the following line:

1
export JAVA_HOME=/usr/lib/jvm/java-8-oracle
-

Start PredictionIO and Dependent Services

If you are using PostgreSQL or MySQL, skip pio-start-all and pio-stop-all, and do PredictionIO-0.10.0-incubating/bin/pio eventserver & instead.

Simply do PredictionIO-0.10.0-incubating/bin/pio-start-all and you should see something similar to the following:

1
-2
-3
-4
-5
-6
-7
$ PredictionIO-0.10.0-incubating/bin/pio-start-all
-Starting Elasticsearch...
-Starting HBase...
-starting master, logging to /home/abc/PredictionIO-0.10.0-incubating/vendors/hbase-1.0.0/bin/../logs/hbase-abc-master-yourhost.local.out
-Waiting 10 seconds for HBase to fully initialize...
-Starting PredictionIO Event Server...
-$
-

You may use jps to verify that you have everything started:

1
-2
-3
-4
-5
-6
$ jps -l
-15344 org.apache.hadoop.hbase.master.HMaster
-15409 org.apache.predictionio.tools.console.Console
-15256 org.elasticsearch.bootstrap.Elasticsearch
-15469 sun.tools.jps.Jps
-$
-

A running setup will have these up and running:

  • org.apache.predictionio.tools.console.Console
  • org.apache.hadoop.hbase.master.HMaster
  • org.elasticsearch.bootstrap.Elasticsearch

At any time, you can run PredictionIO-0.10.0-incubating/bin/pio status to check the status of the dependencies.

Now you have installed everything you need!

You can proceed to Choosing an Engine Template, or continue the QuickStart guide of the Engine template if you have already chosen one.

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/install-sourcecode/index.html.gz ---------------------------------------------------------------------- diff --git a/install/install-sourcecode/index.html.gz b/install/install-sourcecode/index.html.gz deleted file mode 100644 index 0deff6b..0000000 Binary files a/install/install-sourcecode/index.html.gz and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/install-vagrant/index.html ---------------------------------------------------------------------- diff --git a/install/install-vagrant/index.html b/install/install-vagrant/index.html deleted file mode 100644 index 11b9899..0000000 --- a/install/install-vagrant/index.html +++ /dev/null @@ -1,49 +0,0 @@ -Installing PredictionIO with Vagrant (VirtualBox)
On this page
Edit this page

Running PredictionIO with Vagrant is intended for the purposes of simple tests in an isolated environment. Due to resource limitation and overhead of virtual machine (VM), it runs much more slowly or may encounter memory issue. We recommend using Linux or Mac machine for serious usage.

Install VirtualBox

If you don't have VirtualBox installed, please follow the instructions in the VirtualBox site to download and install it. After installation is done, you don't need to setup anything in Virtual Box. Vagrant will do it for you later.

Install Vagrant

If you don't have Vagrant installed, please follow the instructions in the the Vagrant site to download and install it.

Bring up PredictoinIO VM with Vagrant

Get the latest vagrant setup from github and make sure in master branch:

1
-2
-3
$ git clone https://github.com/PredictionIO/PredictionIO-Vagrant.git
-$ cd PredictionIO-Vagrant/
-$ git checkout master
-

Inside the directory PredictionIO-Vagrant/, you will find a file named Vagrantfile which is the configuration file used by Vagrant to setup the VM. You may modify this file if you want to change the VM configuration.

For example, if you want to change the memory of the VM, you can locate the following line in the Vagrantfile and change the value passed to the memory parameter (default is 2048MB):

1
  v.customize ["modifyvm", :id, "--cpuexecutioncap", "90", "--memory", "2048"]
-

In the directory PredictionIO-Vagrant/, bring up PredictionIO VM by running:

1
$ vagrant up
-

When you run vagrant up for the first time, it will download the base box ubuntu/trusty64 if you don't have it. Then it will also install all necessary libraries and setup PredictionIO in the virtual machine.

When it finishes successfully, you should see somthing like the following:

1
-2
-3
-4
-5
-6
-7
-8
-9
-10
-11
==> default: Installation done!
-==> default: --------------------------------------------------------------------------------
-==> default: Installation of PredictionIO 0.10.0-incubating complete!
-==> default: IMPORTANT: You still have to start PredictionIO and dependencies manually:
-==> default: Run: 'pio-start-all'
-==> default: Check the status with: 'pio status'
-==> default: Use: 'pio [train|deploy|...]' commands
-==> default: Please report any problems to: support@prediction.io
-==> default: Documentation at: http://docs.prediction.io
-==> default: --------------------------------------------------------------------------------
-==> default: Finish PredictionIO installation.
-

That's it! Now you have a PredictionIO VM running!

Please see the following notes regarding how to use PredictionIO VM with vagrant.

Using the PredictionIO VM

Login to the VM

You could ssh to the VM by running the following from your host machine in the same directory where you run vagrant up (i.e. PredictionIO-Vagrant/)

1
$ vagrant ssh
-

Then your console prompt becomes something like the following, which means you have logged into the VM:

1
vagrant@vagrant-ubuntu-trusty-64:~$
-

One you've logged into the VM, you can proceed to Choosing an Engine Template or continue the QuickStart of the Engine template you have chosen.

Shutdown and bring up PredictionIO VM again

When you are not using PredictionIO VM, you should shut down VM properly, by running the following in the host machine (not inside VM):

1
$ vagrant halt
-

If you didn't shut down VM properly or you ran vagrant suspend, the VM may go to suspend state. HBase may not be running propoerly next time when you run vagrant up. In this case, you can always run vagrant halt to do a clean shutdown first before run vagrant up again.

Then you can run vagrant up again later to bring up the PredicitonIO VM again.

1
$ vagrant up
-

When it's ready, you should see the following:

1
-2
-3
-4
-5
-6
==> default: --------------------------------------------------------------------------------
-==> default: PredictionIO VM is up!
-==> default: You could run 'pio status' inside VM ('vagrant ssh' to VM first) to confirm if PredictionIO is ready.
-==> default: IMPORTANT: You still have to start the eventserver manually (inside VM):
-==> default: Run: 'pio eventserver'
-==> default: --------------------------------------------------------------------------------
-
\ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/install-vagrant/index.html.gz ---------------------------------------------------------------------- diff --git a/install/install-vagrant/index.html.gz b/install/install-vagrant/index.html.gz deleted file mode 100644 index 1773643..0000000 Binary files a/install/install-vagrant/index.html.gz and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/launch-aws/index.html ---------------------------------------------------------------------- diff --git a/install/launch-aws/index.html b/install/launch-aws/index.html deleted file mode 100644 index 9a1147b..0000000 --- a/install/launch-aws/index.html +++ /dev/null @@ -1,6 +0,0 @@ -Launching PredictionIO on AWS

PredictionIO Docs

Launching PredictionIO on AWS

On this page
Edit this page

Deploying PredictionIO on Amazon Web Services is extremely easy thanks to AWS Marketplace. As long as you have access to AWS, you can launch a ready-to-use PredictionIO Amazon EC2 instance with a single click.

Prerequisites

  • Amazon Web Services account
  • Amazon EC2

Access AWS Marketplace

Visit PredictionIO product's page on AWS Marketplace and sign in with your AWS account.

Using 1-Click Launch

You should see the following screen after you have logged in.

alt text

Under the big yellow "Continue" botton, select the region where you want to launch the PredictionIO EC2 instance, then click "Continue".

alt text

Review your instance's settings before launching. For quick prototyping work, we recommend using the "memory optimized" instances for the cheapest memory configurations at least the "Memory Optimized R3 (r3.large)" or for larger datasets the "(r3.xlarge)".

Setting Security Group

The default security group, marked by "AutogenByAWSMP", has the following ports opened to public:

  • 22 (SSH)
  • 7070 (PredictionIO Event Server)
  • 8000 (PredictionIO Server)
  • 8080 (Spark Master)
  • 9200 (Elasticsearch)

Start Using PredictionIO

It may take a few minutes after the EC2 instance has launched for all PredictionIO components to become ready. When they are ready, you may connect to your instance, see AWS documentation for more details.

Once you connect to your instance, you can find PredictionIO at /opt/PredictionIO and the binary command path is /opt/PredictionIO/bin.

You can proceed to Choosing an Engine Template, or continue the QuickStart guide of the Engine template if you have already chosen one.

< div class="alert-message note">

The AWS instance will have all PredictionIO components automatically started for you, so you could safely skip the pio-start-all command as described in QuickStart.

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/launch-aws/index.html.gz ---------------------------------------------------------------------- diff --git a/install/launch-aws/index.html.gz b/install/launch-aws/index.html.gz deleted file mode 100644 index 502d403..0000000 Binary files a/install/launch-aws/index.html.gz and /dev/null differ http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/sdk/index.html ---------------------------------------------------------------------- diff --git a/install/sdk/index.html b/install/sdk/index.html deleted file mode 100644 index 23792ef..0000000 --- a/install/sdk/index.html +++ /dev/null @@ -1,6 +0,0 @@ -
Edit this page
\ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator-predictionio-site/blob/43f84e11/install/sdk/index.html.gz ---------------------------------------------------------------------- diff --git a/install/sdk/index.html.gz b/install/sdk/index.html.gz deleted file mode 100644 index 9b9f143..0000000 Binary files a/install/sdk/index.html.gz and /dev/null differ