TheRuddyDuck

Install and configure EMC SMI-S Provider on Linux

EMC Storage Management Initiative Specification (SMI-S), is an ANSI standard for storage management. It is a specification that defines an open storage management interface to enable 3rd party and EMC technologies to manage, monitor and control SAN resources. A great example of this is EMC Vipr. Vipr takes physical storage arrays and abstracts them into virtual arrays that provide the basis of software defined storage. SMI-S provides Vipr access to VNX, and VMAX arrays. Future blogs will show how to deploy and setup EMC Vipr for software defined storage using VNX and Isilon. This blog will show you how to install SMI-S on Linux.

First you need to download the file from EMC and upload it to your Linux host. For this demo Im using CentOS 6.4 in a basic install, with SMI-S 7.6.1.1Downloads of the EMC SMI-S provider can be found on support.emc.com

First we have to prep the enviornemnt. SMI-S Provider requires the GNU Compiler Collection (GCC) standard C++. This can be installed with yum yum install compat-libstdc++* The packages listed above will be installed.
Upload the SMI-S file to the /tmp directory. A ls shows the file in the /tmp directory. Extract the file tar xf se7611-Linux-i386-SMI.tar.gz
Install the file. ./se7611_install.sh
The install uses a public key.
After the installer runs, the Solutions Enabler and SMI are shown as installed. SMI tools are located in the /opt/emc directory

Discover resources with SMI-S

Change directory to /opt/emc/ECIM/ECOM/bin
Run the provider ./TestSmiProvider
Enter the connection specifications. You can accept all the defaults. Note the default user and password. This is used by external resources to access SMI
Type dv This lists the version, information, and an discovered arrays
To add a system type addsys For this demo we are adding a VNX. Enter the information for the SP’s, the type of connection, and a user with admin access to the array
The add job runs. You can see the success code 0 and object information about the array is shown. Press enter
Running dv again show the array.

.

Deploy PivotalHD with VMware big Data Extension

One of the benefits of VMware Big Data Extension is the ability to configure, deploy and run multiple Hadoop distributions from different vendors. When you deploy the Big Data Extensions vApp, the Apache 1.2.1 Hadoop distribution is included in the OVA that you download and deployed. You can add and configure other Hadoop distributions, like PivotalHD, using Yellowdog updater (YUM). YUM is an open-source command-line package-management utility for Linux operating systems that allows automatic updates, package and dependency management, on RPM-based distributions like CentOS. PivotalHD and Cloudera distributions require the setup of a YUM repository on the Serengeti vApp management server to host the RPM’s for the hadoop distribution.

This blog will show how to setup PivotalHD for deployment byBDE. To use PivotalHD with VMware Big Data Extensions, you must first setup a YUM repo, and create a CentOS 6 template (See my previous blog on setting up a custom template). The YUM repo holds the RPM’s that are required to install PivotalHD. These RPMS, can be found here:

http://gopivotal.com/pivotal-products/data/pivotal-hd#4

http://bitcast-a.v1.o1.sjc1.bitgravity.com/greenplum/pivotal-sw/phd_1.0.1.0-19_community.tar.gz

VMware Big Data Extension supports PivotalHD version1 on RedHat and derivatives version 6.

After downloading the RPM’s and creating a repo, a configuration script is used to configure the BDE automation. VMware Big Data Extension uses a Ruby script called config-distro.rb located in the /opt/serengeti/sbin directory on the Serengeti vApp management. This script sets up the chef manifests that are used to automate Hadoop cluster deployments. We run this utility and give it the correct distro information for the different packages we want to deploy.

When the Serengeti vApp is deployed, along with the management server VM is a template VM. This VM is a Centos 5 distribution and is used to deploy all the nodes that make up a Hadoop cluster. The management VM uses puppet to deploy the packages to the template and configure it accordingly. PivotalHD is supported on CentOS 6.

Below is how to setup the Serengeti management server for PivotalHD.

Log in to management server using either putty or the VMware console
Change directories to the temp dir  cd /tmp
Download the RPMS from the pivotal web site using the wget command wget bitcast-a.v1.o1.sjc1.bitgravity.com/greenplum/pivotal-sw/phd_1.0.1.0-19_community.tar.gz
Extract the content of the downloaded file tar -zxvf phd_1.0.1.0-19_community.tar.gz
There will be some errors with the content as it extracts. This is normal.
Once extraction is complete, change directories cd PHD_1.0.1_CE
There are 3 files in this directory that need to be extracted. tar -xf PHD-1.0.1.0-19.tar.gz tar -xf PHDTools-1.0.1-19.tar.gz tar -xf PCC-2.0.1.84.121.163.x86_64.tar.g
Once the files are extracted, create a directory to place the RPMS and copy the files to that directory mkdir -p /opt/serengeti/www/PHD/1 mv PHD-1.0.1.0-19 /opt/serengeti/www/PHD/1/ mv PCC-2.0.1.84 /opt/serengeti/www/PHD/1/ mv PHDTools-1.0.1-19 /opt/serengeti/www/PHD/1 cd /opt/serengeti/www/PHD/1/
A list show the 3 directories moved in the last step.
Create a YUM repo by executing the following command: createrepo .
Create and edit the repo file touch PHD.repo vim PHD.repo
Enter the following into the file [PHD] name=Pivotal HD Version 1 baseurl=https://10.10.81.36/PHD/1/ enabled=1 gpgcheck=0 protect=1 NOTE: baseurl should be the IP address of the management server. An ifconfig from the command line will give you this address. Save file.
Open a browser and enter the url: https://10.10.81.36/PHD/1/PHD.repo   You should see the contents of the repo file from the last step.
Use the config-distro.rb command to create the correct setting for the Chef manifest config-distro.rb --name PivotalHD --vendor PHD --version 1.0.1 --repos http://10.10.81.36/PHD/1/PHD.repo
Change directory and run the cat command on the manifest file to check contents: cd /opt/serengeti/www/distros cat manifest The end of the file should contain the same text as the screen shot above. Also contained in this directory is a file called manisfest.sample, that shows a sample of how distributions should appear in the manifest file.
Change directory and edit the map file: cd /opt/Serengeti/www/specs vim map
Scroll through the file till you find the “PHD” section. Verify that the version number is the same that you downloaded and set the repo up with. Close file without saving
Restart tomcat service service tomcat restart
In the VMware web client, go to the Big Data extensions tab and click on Hadoop Distributions. You should see the PivotalHD distribution version 1.2.1 is now ready. This verifies the contents of the manifest file. You will always have the apache distribution listed in addition to any other configures distributions.
Click on the Big Data Clusters tab, and select deploy cluster. Under the Hadoop distribution drop down select Cloudera. All deployment types should be available. This verifies the contents of the map file.  Check out the EMC Hadoop starter kit for more information https://community.emc.com/docs/DOC-26892

Create a Custom Template for VMware Big Data Extension

The Serengeti vApp deployed for use by VMware Big Data extension comes with two VM’s. The management VM, that contains all the CHEF recipes and manifests used for automating deployments, and a Template VM, used to deploy all the nodes of a Hadoop cluster. The template VM comes with CentOS 5 as the installed OS. You can create a Hadoop Template virtual machine using a customized version of CentOS 6.x OS. This allows you to deploy an operating system with configurations specific to your IT environment. You can create a Hadoop Template virtual machine using a version of CentOS 6.x Linux customized for your IT environment in combination with a supported Hadoop distribution. This allows you to create a Hadoop Template virtual machine using your organization's preferred operating system configuration. When you provision Big Data clusters the customized CentOS operating system will be used in the virtual machines that are created from the Hadoop Template virtual machine.

PivotalHD deployments require CentOS 6, so to deploy PivotalHD you will have to create a custom tempalte. The Table below shows the supported Hadoop Distributions by VMware Big Data Extensions. If you choose to use the custom template with CentOs6, make sure you download the appropriate Hadoop versions. It is alos possible to drab and drop the appropriate template back and forth depending on the Hadoop distributions supported OS type, although obviously this is  a manual proccess.

 The rest of this blog shows setting up a custom CentOs 6.4 template

 

Using the vCenter client, create a new Virtual Machine. Select Typical and click Next
Give the Template VM a descriptive name and choose an Inventory location. Click Next
Select a location for the template vm. It should be on shared storage. Click Next
Select Linux as the guest operating systems with “Red Hat Enterprise Linux 6 (64-bit)” as the version Click Next
Use the default Adapter and connect it to the correct network. This network should be reachable by vCenter and the Serengeti Management VM. Click Next
Create a disk size of 20 gigs Click Next
Review the setting and click Finish.  Once the VM creation is finished, power on the VM and open the console.
Click the CD button and navigate to your CentOS 6.x image. CentOS images can be downloaded from: http://wiki.centos.org/Download For this install we will be using CentOS version 6.4
From the splash screen select Install. We wont walk through all the steps of Installing the OS. The Template requires a basic Install so the defaults are used. We will highlight some points of interest.
There is no need to give the template a host name. Host names are assigned by Big Data extension during deployment. For IP address we will want to use DHCP. Templates deployed by BDE use either DHCP or a IP address pool to assign IP’s. During the configuration of the template we will require access to the internet. If you do not have DHCP, assign a temporary IP address. Remember to set the address back to DHCP after configuration. Select Basic Server for Install.
After the install completes logon to the console. Edit the network file: vi /etc/sysconfig/network-scripts/ifcfg-eth0
Change the ONBOOT to equal yes If you are using a DHCP IP address, the ifcfg-eth0 file should look like the screen shot above when configuration is complete.
Bring up the interface with this command ifup eth0
Install the wget utility. yum install wget
Change into the temp directory cd /tmp Retrieve the java installer using wget wget https://mrplus.googlecode.com/files/jdk-6u31-linux-x64.bin --no-check-certificate NOTE: By retrieving the Java installer from a google repository we can avoid the hassle of downloading it from Oracle then uploading it to the VM .
Change the attribute on the downloaded file: chmod a+x jdk-6u31-linux-x64.bin Make a directory to install java: mkdir /usr/java mkdir /usr/java/default Move the java installer to this directory: mv jdk-6u31-linux-x64.bin /usr/java/default Change into that directory: cd /usr/java/default
Install java:  ./ jdk-6u31-linux-x64.bin
Next Install VMware Tools. On the console click the VM tab, select guest and Install/Upgrade VMware Tools	1)
From the command line mount the cdrom mount /dev/cdrom /media
Change directories to media cd /media
Copy the VMware tools installer to the temp directory cp VMwareTools* /tmp
Extract the VMwaretools tar file tar –zxvf VMwareTools*
Change into the vmwaretools directory and execute the installer cd /vmware-tools-distrib ./vmware-install.pl
After the installer is done change into the temp directory and download the custom scripts from the mangemnet server cd /tmp wget https://10.10.81.36/custos/custos.tar.gz --no-check-certificate Note: Replace the IP address with the IP address of your management
Extract the contents and execute the file. tar xf custos.tar.gz ./installer.sh /usr/java/default/jdk.1.6.0_31
When the install completes, add the java path to the environment echo “JAVA_HOME=/usr/java/default/jdk1.6.0_31 “ > etc/environment
Turn the firewall off service iptables off chkconfig iptables off
If you have set a temporary IP address, set it back to DHCP. Remove the 70-persistent-net.rules file and power down the template VM. rm /etc/udev/rules.d/70-persistent-net.rules NOTE: Removing this file keeps cloning jobs from changing the Ethernet interface number. This is the last command to run before turning the template off
On the vcenter client, drag and drop the new template into the vApp. Then Drag and drop the old template out of the vApp On the management server, restart the tomcat service service tomcat restart   BDE will now deploy Hadoop distributions to the new CentOS 6 template.  Verify that your Hadoop distributions are for CentOS 6. PivotalHD requires version 6, other distributions have seperate packages for either version 5 or 6. The default apache distro, and my previous posts, have shown version 5 deployments. For now you can run the last 2 steps per distro (drag and drop). Hopefully in the future BDE will add support for multiple templates

Deploy Cloudera with VMware Big Data Extension

In previous posts I showed how to setup VMware Big Data extension, and integrate it with Isilon for HDFS. This blog will show you how to use BDE to deploy Cloudera.

One of the benefits of VMware Big Data Extension is the ability to configure, deploy and run multiple Hadoop distributions from different vendors. When you deploy the Big Data Extensions vApp, the Apache 1.2.1 Hadoop distribution is included in the OVA that you download and deployed.  You can add and configure other Hadoop distributions, like Cloudera’ s distribution version 4 (CDH4), using Yellowdog updater (YUM). YUM is an open-source command-line package-management utility for Linux operating systems that allows automatic updates, package and dependency management, on RPM-based distributions like CentOS. Cloudera and PivotalHD distributions require the setup of a YUM repository on the Serengeti vApp management server to host the RPM’s for the hadoop distribution.

This blog will show you how to setup Cloudera CDH4 for automated deployments by BDE. To setup CDH4 you must first setup a YUM repo. The repo holds the RPM’s that are required to install CDH4. These RPMS, and the associated gpgkey can be found here:

http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/4.2.2

http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/RPM-GPG-KEY-cloudera

VMware Big Data Extension supports CDH4 version 2.x on RedHat and derivatives version 5

After downloading the RPM’s and creating a repo, a configuration script is used to configure the BDE automation. VMware Big Data Extension uses a Ruby script called config-distro.rb located in the /opt/serengeti/sbin directory on the Serengeti vApp management. This script sets up the chef manifests that are used to automate Hadoop cluster deployments. We run this utility and give it the correct distro information for the different packages we want to deploy.

When the Serengeti vApp is deployed, along with the management server VM is a template VM. This VM is a Centos 5 distribution and is used to deploy all the nodes that make up a Hadoop cluster. The management VM uses chef to deploy the packages to the template and configure it accordingly.

Log in to management server using either putty or the VMware console
Install the createrepo utility. Type the following at the command line: yum install –y yum-utils createrepo
Change directory cd /etc/yum.repos.d/ Create repo file touch cloudera-cdh4.repo Edit file vim cloudera-cdh4.repo
Enter the following : [cloudera-cdh4] name=Cloudera's Distribution for Hadoop, Version 4 baseurl=http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/4.2.2 gpgkey =http://archive.cloudera.com/cdh4/redhat/5/x86_64/cdh/RPM-GPG-KEY-cloudera gpgcheck = 1 Write information to file
Create a local repo by synching the repo file with Cloudera source code: reposync –r cloudera-cdh4 This command will retrieve the RPM’s from the internet.
List directory show newly created cloudera-cdh4 directory with RPM’s: ls
Create a directory for the RPMs’ mkdir –p /opt/Serengeti/www/cdh/4 Move downloaded RPM’s to this directory mv cloudera-cdh4/RPMS/ /opt/serengeti/www/cdh/4/
Change directory and look at contents: cd /opt/Serengeti/www/cdh/4 ls
Create a Cloudera repo that is published by the apache service: createrepo .
A ls shows the repodata directory has been created
Create a repo file vim cloudera-cdh4.repo
Enter the following into the file [cloudera-cdh4] name=Cloudera's Distribution for Hadoop, Version 4 baseurl=http://10.10.81.36/cdh/4/ enabled=1 gpgcheck=0 NOTE: baseurl should be the IP address of the management server. An ifconfig from the command line will give you this address. Save file
Open a browser and enter the url: https://10.10.81.36/cdh/4/cloudera-cdh4.repo   You should see the contents of the repo file created in the last step
Use the config-distro.rb command to create the correct setting for the Chef manifest config-distro.rb --name Cloudera --vendor cdh --version 4.2.2 --repos http://10.10.81.36/cdh/4/cloudera-cdh4.repo
Change directory and run the cat command on the manifest file to check contents: cd /opt/serengeti/www/distros cat manifest The file should have the same settings as the screen shot on the left. The file will also contain setting for Apache, and any other distributions you have setup.
Change directory and edit the map file: cd /opt/Serengeti/www/specs vim map
Scroll through the file till you find the “CDH” section. Verify that the version number is the same that you downloaded and set the repo up with. Close file without saving
Restart tomcat service service tomcat restart
In the VMware web client, go to the Big Data extensions tab and click on Hadoop Distributions. You should see the Cloudera distribution version 4.2.2 is now ready. This verifies the contents of the manifest file
Click on the Big Data Clusters tab, and select deploy cluster. Under the Hadoop distribution drop down select Cloudera. All deployment types should be available. This verifies the contents of the map file.   To download the EMC Hadoop starter kit that shows configuring BDE with Isilon for HDFS and configuration of Cloudera go to the following link: https://community.emc.com/docs/DOC-26892

Deploy Hortonworks Data Platform with VMware Big Data Extension

In previous posts I showed how to setup VMware Big Data Extension, and integrate it with Isilon for HDFS. This blog will show you how to use BDE to deploy Horonworks data platform (HDP)

When you deploy the Big Data Extension (BDE) vApp, the Apache 1.2.1 Hadoop distribution is included in the OVA that you download and deploy. You can add and configure other Hadoop distributions, like Hortonworks Data Platform (HDP), using the command line. One of the benefits of VMware Big Data Extension is the ability to configure, deploy and run multiple Hadoop distributions from different vendors.

To setup HDP you must first download the tar ball distributions from the repo web site. The website is:

http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/

Browsing the website you can see links to different versions, documentation, and utilities. For this blog we use 1.07, but all versions should work.

VMware Big Data Extension uses a Ruby script called config-distro.rb located in the /opt/serengeti/sbin directory on the Serengeti vApp management server to retrieve the tar ball packages and set up the puppet manifests used to automate deployment. We run this utility and give it the correct URL information for the different packages we want to deploy.

When the Serengeti vApp is deployed, along with the management server VM is a template VM. This VM is a Centos 5 distribution and is used to deploy all the nodes that make up a Hadoop cluster. The management VM uses chef to deploy the packages to the template and configure it accordingly. In future blogs Ill show you how to make a custom template using CentOS 6. If you use it, you would then also have to use the correct HDP distro

We use the following URL to retrieve the 1.0.7 packages for Centos 5:

Hadoop : http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hadoop-1.0.2.tar.gz

Pig: http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/pig-0.9.2.tar.gz

Hive: http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hive-0.8.1.tar.gz

Hbase: http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hbase-0.92.0.tar.gz

Zookeeper: http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/zookeeper-3.3.4.tar.gz

Log in to management server using either putty or the VMware console
Run the config-distro command with the correct options.The config-distro.rb command has the following options (Note this is all one line) config-distro.rb --name HortonWorksHDP --vendor HDP --version 1.0.7 --hadoop http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hadoop-1.0.2.tar.gz --pig http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/pig-0.9.2.tar.gz --hive http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hive-0.8.1.tar.gz --hbase http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/hbase-0.92.0.tar.gz --zookeeper http://public-repo-1.hortonworks.com/HDP-1.0.7/repos/centos5/tars/zookeeper-3.3.4.tar.gz --hve true	.
After the command is executed the packages are retrieved and placed in the proper directory on the management server, and the chef manifest is updated.
Change directory to the /opt/serengeti/www/distros directory. Do list (ls) and you should see a directory with the name used by the config-distro.rb command. You will also see a file called “manifest”
Open the manifest file with a text editor. In this example we use vim
v Look through the files. The manifest now contains the correct information for chef to use to retrieve the packages during automated deployment.
Change directory to /opt/serengeti/www/specs List the directory (ls). You see directories that contain different information for hadoop distributions and a file called map. Open the map file with a text editor
Scroll through till you find the section for “HDP”. There are 4 sections. Each section represents a configuration option during deployment. Make sure the version listed is the same as the package you retrieved. If it is not, edit it. Exit without saving.
Restart the tomcat service service tomcat restart
In the web client, under the Big Data extension tab, click on Hadoop Distributions
Verify the distribution you just configured is present   To download the EMC Hadoop starter kit that shows configuring BDE with Isilon for HDFS and configuration of HDP go to the following link: https://community.emc.com/docs/DOC-26892

 

EMC Hadoop Starter Kit

I began working at the EMC Open Innovations lab (OIL) in July, and our first project was to work with the Isilon business unit to help support Big Data initiatives. We started with 2 projects, Deploying Splunk on Isilon reference architecture ( SPLUNK) and the EMC Hadoop starter kit (HSK)! The HSK utilizes VMware big data extension (BDE) to automate deployment of all the major hadoop distributions (PivotalHD, Apache, Cloudera, Hortonworks) in a VMware environment. It then show how to use EMC Isilon storage for native HDFS storage. The point of the guide was to enable someone (like myself), who had no experience with hadoop or big data, to rapidly deploy hadoop environments using already existing equipment. If you have a VMware environment, and you own and Isilon array, you can deploy HSK in about an hour. The guide is meant to help a real world IT issue, Shadow IT. Since most infrastructure guys and gals are not programmers, there is a significant ramp up time for IT to deploy hadoop clusters. This includes learning, testing, and procurement of “commodity” hardware (which requires a budget). What we’ve seen in the field is that many hadoop projects were starting in Amazon as IT was seen as a road block to beginning Hadoop projects.

Here is a demo of the HSK: 

 

 

And the download link:

https://community.emc.com/docs/DOC-26892

Upgrade onefs

This blog will show you how to upgrade your existing Isilon cluster. Recently I’ve been in the lab testing Hadoop distributions. For Hadoop HDFS the supported versions are as follows:

Isilon OneFS version 6.5.5 and greater supports HDFS.

Isilon OneFS 7.0.1.5 and greater supports HDFS version 2.

We did all are testing using 7.0.2.2 and wanted to verify 7.0.2.4. Once you’ve acquired the upgrade file from Isilon, here is the upgrade process

Logon to the cluster. In the upper right corner click Help and About This Cluster
Under the About this Cluster section you will see the Upgrade link. Click it
On the upgreade screen, click Browse
Isilon needs local access to the installer file. You can upload it to the ifs directory with CIFS, NFS, winscp, or HDFS. The screenshot above shows uploading the file using the vCenter NFS mount point
Browse to the folder where you placed the file. Click it and click OK
The directory and file info will be filled out. Clck Submit
The upgrade begins
The precheck runs. We see some warnings on our cluster. Open a ssh connection to the cluseter and run “isi event list” to view the warnings
The warning on our cluster were due to temp licenses. We can ignore this and continue
After clicking Yes the upgrade continues
We are asked whether we want to simultaneously upgrade all nodes in the cluster, or perform a Rolling Upgrade, one node at a time. Since we are in an active lab we “Rolled” our upgrade. Click Continue
Nodes are upgraded. After completion the cluster is rebooted.
Once the reboot is complete, log back into the cluster and verify that onefs has been upgraded.

Mapred permissions and EMC Isilon

When using HDFS on Isilon, only one user needs to be created for hadoop to access HDFS, “mapred”. This user is used by the jobtraker and used when mapredcuce jobs are submitted. Interesting thing is that if you run a

hadoop fs –ls /

command, this is done under the credentials you are logged in with. Mapred is only used when jobs are submitted. To create the user and add it to the wheel group on Isilon:

This is done from the CLI of the Isilon cluster. The other interesting thing is that when you submit a mapreduce job the first time, a /tmp directory is created in the root HDFS directory.

 

It is created with the mapred user as the owner and wheel as the group. I have verified that Hortonworks, Apache, and Cloudera all create this file structure properly. Cloudera needs this directory structure setup. Here is how you do it:

Configuring HDFS to access EMC Isilon storage

In the last blog post I showed how to configure your EMC Isilon cluster for HDFS. This post will show how to setup Hadoop to utilze Isilon for HDFS.

There are 2 files that contain the HDFS configuration information. These files are in the hadoop/conf directory. There location will depend on where you installed hadoop. In the example below they are located in the /etc/hadoop/conf directory.

Location of the files core-site.xml and hdfs-site.xml. Use your favorite editor to access and change the settings

Core-site.xml contains the fs.default.name entry. To connect it to Isilon it should read

<name> fs.default.name</name>

<value>hdfs://FQDNofISILON:8020</value>

</property>

The hdfs-site.xml file  should read

<property>

<name>dfs.http.address</name>

<value>FQDNofISILON:50070<value>

</property>

 

 

There is no service to restart as the config file is reloaded for every request to HDFS.

Integrating VMware Big Data Extension with EMC Isilon

When deploying a Hadoop cluster with VMware big data extensions (BDE), you have a few options on the type of cluster you deploy. The deployment types supported by BDE are Basic, HBase, Data/Compute separation, and Compute-only. To integrate EMC Isilon for HDFS we use the compute-only deployment type

Deployment types are pre-defined in BDE. You can view these types by looking at the map file found in the /opt/serengeti/www/specs directory of the Serengeti vApp management server.

The diagram below shows the contents of the map file for PivotalHD. Each deployment type is defined with the vendor name, version #, Deployment type, and path to the json file for that type.

To deploy a compute only hadoop cluster and map HDFS to Isilon follow the steps below

See my preivous blog post on how to setup Isilon for HDFS

Log in to the vSphere Web Client. Select Big Data Extensions. Click Create a New Hadoop Cluster from theBasic Tasks list in theGetting Started tab. The Create New Hadoop Cluster dialog displays.
Give the cluster a name. Select a distribution Select Compute-Only Hadoop Cluster
Enter the HDFS RPC URL to the Isilon cluster. Format: HDFS://IsilonFQDN:8020
Select the resource size for the nodes. By default the Compute Master and theClient Node will be placed on shared storage. To change this, select customize on the dropdown and choose local storage. Workers are placed by default on local storage.
Select a resource pool for deployments
Choose Network
Cluster will begin deploying
After deployment you can check that HDFS is using Isilon by issuing the following command from any node. This command lists the contents of the HDFS directory on Isilon hadoop fs –ls /

 

 

See my previous blog post on how to setup Isilon for HDFS.  The example illustrates PivotalHD, but can be used by any distribution that has been configured (future blog posts will cover configuring hadoop distributions). For a full detailed doc on BDE deployments download the EMC hadoop starter kit:

https://community.emc.com/docs/DOC-26892