Oracle Big Data Cloud Platform...o 172.16.0.0/12 o 192.168.0.0/16 Note: In case customer’s network overlaps with any of the subnets above, they must mask their internal systems with

Oracle Big Data Cloud Platform Guide for provisioning and accessing BDDCS A L Y S S O N S O U Z A | F E B R U A R Y 2 0 1 7

ORACLE BIG DATA CLOUD PLATFORM

Disclaimer

The following is intended to guide Oracle Big Data Discovery Cloud Service subscribers through the

steps to provision the service and access the Studio console. This is NOT an official or supported

documentation.

1 | ORACLE BIG DATA CLOUD PLATFORM

Creating a Big Data Cloud Service Instance

The first step in order to enable access to all BDCS and BDDCS services is the

creation of a Big Data Cloud Service instance. This process will allocate the resources on

OPC that will be lately used for the deploy and configuration of a CDH cluster.

To do this a user with Big Data Administrator role must access My Services

dashboard and choose the BigData service from the “Create Instance” menu.

You will be prompted for the following configuration details and after filling this

information you will be able to pick the “Create Service Instance” button.

1. Instance Details

• Name – Enter a name for the service instance

• Plan – Only one option available and will be selected by default

• Starter Pack - Only one option available and will be selected by

default

• Additional Nodes – Number of additional nodes on subscription

2. Administrator Details

• E-mail – E-mail address for this instance’s administrator

• First/Last Name – First and last name of the user

The allocation of resources usually takes a few minutes (notification will be sent

by e-mail) and you must wait for this process to be finished before going to the next step.

Creating a Hadoop Cluster


After the resources are allocated you will be able to create a CDH cluster using

those resources.

Go to My Services dashboard and select “Open Service Console” from the BigData

service menu.

From this page you can start the cluster creation process by picking the “Create

Cluster” button.

You will be prompted for following configuration information and once this is filled

the cluster creation will start.

1. Cluster Details

• Name – Cluster’s name

• Description – Description for the cluster

• Big Data Appliance System – Resource configuration for this cluster

2. Security

• SSH Key – You must upload a public SSH Key so OPC user can be

authenticated later when accessing the cluster nodes

• Cloudera Administrator Password – Password definition for accessing

Cloudera Manager

• Kerberos – Choose to enable or not Kerberos on this cluster

3. Storage

• Storage User Name – Enter the string with information for

authenticating with Storage Cloud Service

• Storage Password – User’s password


Note: Configuring Storage Cloud Service is not mandatory for the Cluster

creation

This process usually takes a few hours to be finished.

Raising the VPN Provisioning SR

Having a cluster created is mandatory before you are able to start the VPN

provisioning process.

Since this configuration is done directly on Oracle’s datacenter you must raise a

SR on My Oracle Support and submit a spreadsheet with the required information from

customer’s side configuration.

The form that must be filled is named Standard Oracle Cloud Network VPN Form

and can be found on this page:

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=300057287309280

&id=2056914.1&_afrWindowMode=0&_adf.ctrl-state=17rlub7ghc_4

A few points of attention before submitting the form to MOS are:

• All fields in blue must be filled, including contact information

• On sheet’s bottom you can find all the supported encryption and hash algorithms

• To avoid conflict with Oracle’s internal network the specified “Remote

Subnet(s)” must not be in the RFC 1918 address range, which are:

o 10.0.0.0/8

o 172.16.0.0/12

o 192.168.0.0/16

Note: In case customer’s network overlaps with any of the subnets above,

they must mask their internal systems with a public IP or a different subnet

and them fill the spreadsheet’s “Remote Subnet(s)” field with a valid value.

Once all the required information on the spreadsheet is filled, a CSI admin must

raise a SR on MOS through the page: support.oracle.com. The required fields for raising

the SR are shown in the image below.


Note: Under the “Service” field customer should select the Identity Domain where

BDCS is available

Once the SR is created a collaborative SR will be raised by the analyst with Net

Ops who will evaluate the information on the spreadsheet and schedule an implementation

date so the configuration is implemented on Oracle’s datacenter. This process usually

takes between 1~2 weeks to be concluded and once finished customer will be informed

through the SR.

Sometimes, even after the configuration is finished, the VPN tunnel is not active

and a troubleshooting call between a Net Ops engineer and the customer must be

scheduled to check what is causing the issue. To schedule this call customer must update

the SR with a date suggestion.

PS: If it’s taking too long for the call to be scheduled it’s possible to contact Net

Ops engineers internally using the Pidgin group: cloud-networks-chat

It will be requested the SR number that was created by the support analyst with Net Ops

so the available engineer can follow what has been made so far.

You can go to the next steps before the VPN setup is finished.

Creating the BDDCS Instance

After the CDH cluster is successfully created you can create the BDDCS instance.

On My Services dashboard pick the “Create Instance” button and choose BDDCS.

For this service you will be prompted for the following information:


1. Service

• Big Data Discovery Cloud Service Name – A name to identify your

instance

• Description – An optional description to the instance

• Big Data Cloud Service Instance – A Big Data Cloud Service cluster

on which BDDCS will be deployed

2. Backup Details

• Storage Service URL – A valid URL for Storage Cloud Service. It can

be obtained by accessing Dashboard > Storage > Service Detail >

Service REST Endpoint

• Storage Container – Name of the container on Storage Cloud Service

where backups will be stored

• Storage User Name – A user with Storage Admin role

• Storage Password – Password for this user

Note: Make sure you set the replication policy for this service before

which can be done on the Service Detail page

3. Hadoop Details

• User name – Username of an existing Cloudera Manager user.

Default user for CM is ‘admin’

• Password – Password for this user. If using ‘admin’ user the password

was specified during the cluster creation

• Hive Database Name – Name of a Hive database which BDD will

regularly scan for data. The default value is the database ‘default’

4. WebLogic Administrator

• User name – New WebLogic Server Administrator username for

BDDCS

• Password – Password for this user

• Confirm Password – Confirm the password

5. Studio Administrator

• E-mail address – Valid e-mail address that will be used as the

administrator for BDDCS Studio


• Password – Define a password for this user


6. Studio Database User

• User name – Enter a new Studio database user name

• Password – Define a password for this user


Once you correctly entered all the required information you will be sent to a

Confirmation Page in which you will be able to start the creation of the BDDCS instance.

This process usually takes a little over an hour.

Accessing BDDCS Studio Before the VPN Setup is Finished

Since it could take up to two weeks for the VPN setup to be finished and customer

might have the need to start using the service earlier there it is possible to enable access

to BDDCS studio using SSH tunneling.

Studio runs by default on port 7004 from node 5, which by default is closed to any

access outside the VPN. To enable access to this port without the VPN you should first

enable the forwarding of TCP packets.

On node 5 execute the following steps:

1. As root user edit the TCP forwarding parameter of sshd_config file under

/etc/ssh/sshd_config

AllowTcpForwarding yes

2. Reload and restart sshd

# cd /etc/inid.d/

# ./sshd reload

# ./sshd restart


3. Create a SSH tunnel to port 7004 of node 5

On UNIX:

$ ssh –i private_key opc@NODE5_IP –L 7004:localhost:7004

On Windows using PuTTY:

After the tunnel is created you can access the service from the local browser using the

URL: https://localhost:7004/bdd



References

http://docs.oracle.com/cloud/latest/bigdata-cloud/

http://docs.oracle.com/cloud/latest/big-data-discovery-cloud/

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=300057287309280

&id=2056914.1&_afrWindowMode=0&_adf.ctrl-state=17rlub7ghc_4

Documents

Oracle Big Data Cloud Platform...o 172.16.0.0/12 o 192.168.0.0/16 Note: In case customer’s network overlaps with any of the subnets above, they must mask their internal systems with