• No results found

User Manual: Using Hadoop with WS-PGRADE. workflow.

N/A
N/A
Protected

Academic year: 2021

Share "User Manual: Using Hadoop with WS-PGRADE. workflow."

Copied!
6
0
0

Loading.... (view fulltext now)

Full text

(1)

User Manual: Using Hadoop with WS-PGRADE

workflows

December 9, 2014

1

About

This manual explains the configuration of a set of workflows that can be used to submit a Hadoop job through a WS-PGRADE portal. The work-flow automatically creates the Hadoop cluster in an OpenStack cloud and executes the Hadoop job there. The user only needs to provide job input files and two configuration files for specifying cluster and job parameters.

Two methods can be used for submitting a Hadoop job through a WS-PGRADE portal:

1. Single Node Method

The Single Node method uses a single node workflow with a simple program to create Hadoop clusters in an openstack infrastructure, ex-ecute jobs in the cluster and retrieve results.

2. Three Node Method

The Three Node method works the same way as the Single Node method, but divides the task into three stages. The first stage cre-ates the Hadoop cluster, the second executes the Hadoop job and the third destroys the cluster. Each stage can be considered as a work-flow node executing a particular task. The main idea behind dividing the complete process into three stages was to allow the user to deploy Hadoop before executing a job and not at the time of executing a job. In addition, it allows for reusibility of the Hadoop cluster, as the user can keep on adding execute nodes, one after the other. An added ad-vantage is that the user can place these three nodes anywhere in the workflow.

(2)

2

Prerequisites

1. Access to any CloudBroker Platform

2. Access to any WS-PGRADE (gUSE) portal configured to submit jobs to the CloudBroker Platform

3. Access to any Openstack cloud configured to submit jobs using the CloudBroker Platform

4. Hadoop application pre-deployed in CloudBroker platform

3

Single Node Method

1. Log in to the WS-PGRADE portal, select the import option under the Workflow tab and select Remote SHIWA Repository

2. From the list of public bundles, find and import bundle named ’Hadoop’ 3. Select the workflow tab and click on the configure button for the new

imported workflow

4. In the Job Executable tab find the deployed Hadoop application and configure the parameters as desired

5. Download configuration files from here

6. Fill details in the job.cfg and cluster.cfg config files

7. Copy your Hadoop job executable (jar file) in the same folder

8. Copy your Hadoop job input files in a folder called input, compress this folder to create a tar archive called input.tar and copy this compressed file to the same folder as before

9. Copy your OpenStack credentials file to the same folder. Make sure that your password is hardcoded in the file.

10. Compress the configuration files, job executable, compressed job input file and OpenStack credentials file as a tar file called Data.tar

11. In the Job I/O tab, now scroll down to Port 3 settings and upload the Data.tar file

12. Remember to save and upload the new configuration 13. You can now submit the workflow from the Workflow tab

(3)

4

Three Node Method

Figure 1: Three Node basic configuration

1. Download configuration files from here

2. Fill details in the job.cfg and cluster.cfg config files

3. Copy your Hadoop job executable (jar file) in the same folder

4. Copy your Hadoop job input files in a folder called input, compress this folder to create a tar archive called input.tar and copy this compressed file to the same folder as before

5. Copy your OpenStack credentials file to the same folder. Make sure that your password is hardcoded in the file.

6. Log in to the WS-PGRADE portal and create a workflow according to your application (Configurations for each Node are given below) 7. Place the Create Node before the first Execute Node and place the

(4)

8. Connect the output(channel) port of the Create Node to the input(channel) port of the first Execute Node

9. Connect the output(channel) port of the First Execute Node to the input(channel) port of the next Execute Node and repeat for every Execute Node.

10. Connect the output(channel) port of the last Execute Node to the input(channel) port of the Destroy Node

4.1 Create Node

1. This node should have 3 input ports and 1 output port (port 0-2 as input and 3 as output)

2. Download input scripts from here 3. Configure node as follows:

(a) Job Executable

i. Type: cloudbroker

ii. Name: The name of the platform iii. Software: Hadoop 1.0

iv. Executable: Hadoop 1.0 hadoop test.sh

v. Fill resource, region and instance type according to your re-quirements

(b) Job I/O

i. Port 0 input file: hadoop.sh (For each port, please enter the internal file name to be the same as the input file name) ii. Port 1 input file: create.sh

iii. Port 2 input file: Data.tar (Compress the cluster.cfg and OpenStack credentials file as a tar file named Data.tar) iv. Port 3 output(channel) file: job.id

4.2 Execute Node

1. This node should have 4 input ports and 2 output port (port 0-3 as input and 4-5 as output)

(5)

3. Configure node as follows: (a) Job Executable

i. Type: cloudbroker

ii. Name: The name of the platform iii. Software: Hadoop 1.0

iv. Executable: Hadoop 1.0 hadoop test.sh

v. Fill resource, region and instance type the same as in the Create Node

(b) Job I/O

i. Port 0 input(channel) file: job.id

ii. Port 1 input file: hadoop.sh (For each port, please enter the internal file name to be the same as the input file name) iii. Port 2 input file: execute.sh

iv. Port 3 input file: Data.tar (Compress the configuration files, job executable, compressed job input file and OpenStack cre-dentials file as a tar file named Data.tar)

v. Port 4 output(channel) file: job.id

vi. Port 5 output file: output.tar.gz (Hadoop job output folder as compressed archive)

4.3 Destroy Node

1. This node should have 3 input ports 2. Download input script from here 3. Configure node as follows:

(a) Job Executable

i. Type: cloudbroker

ii. Name: The name of the platform iii. Software: Hadoop 1.0

iv. Executable: Hadoop 1.0 hadoop test.sh

v. Fill resource, region and instance type same as in the Create Node

(b) Job I/O

(6)

ii. Port 1 input file: hadoop.sh (For each port, please enter the internal file name to be the same as the input file name) iii. Port 2 input file: Data.tar (Compress the cluster.cfg and

References

Related documents

The FPGA, is the heart, encoding input image data into a compressed output, used to create a JPEG image file.. The DSP handles transactions between the PC and FPGA core,

programs require input data (i.e., your pedigree file) to be a delimited ASCII text file or Excel spreadsheet in which each line of the file contains information on a single

The router receives the request, and using its settings creates a tunnel for data transfer to the air han- dling unit with an IP address on the local area network 192.168.0.50 and

HIVE Regular input: 1~5GB/ 5min 1 hour Table Parse accumulated data per hour, using MapReudce job 5 min Data file History. Data Actor Info Album

The USB Data Link cable is your fast solution to peer-to-peer file transfer between two computers via the USB port.. The USB Data Link cable provides true plug-n-play capability

Enable this function, and fill in the camera’s IP address under “Private IP”’ (or similar field), select “TCP” or “BOTH” as the data type, and input these port numbers

(Note: the choice of input signal sources, the output signal and the output channel type configuration for the machine stored total volume not save scene data load operation).