Deploying a Oracle NoSQL Cluster by using Raspberry Pi

1. Start the SD Formatter tool.

2. Insert the SD memory card into your computer or connect it to your computer by using an SD card peripheral. Wait until you see the drive letter in the SD Formatter tool, then click Option.



3. In the Option Setting dialog box, select FULL (Overwrite) for Format Type and ON for Format Size Adjustment, and then click OK.

   

4. Click Format to start the SD Formatter tool.

   

5. Click OK to format the SD memory card.

   

   A dialog box displays the progress of the format.

   

6. When the format is complete, click OK to close the dialog box.

   

7. Eject the SD Card. Perform steps 2 through 6 in the other two SD cards.

   

8. Perform steps 2 through 7 in the other two SD cards.

9. Click Exit to close the SD Formatter tool.

   

You are now ready to install the Raspbian Wheezy image in the SD memory card.

1. Open an unzip tool and extract the contents of the Raspbian Wheezy zip file 2015-05-05-wheezy-raspbian.zip.

   

2. Start the Win32DiskImager application.

   

3. Make sure that the SD card is inserted and the device address is the same as the mount point for the SD memory card.

   

4. Click the folder button, navigate to the location of the image file, and click Write.

   

5. Click Yes to confirm that you want to overwrite the contents of the SD memory card.

   

   A progress meter is displayed.

   

6. When the Write Successful message is displayed, click OK.

   

7. Remove the SD card from the computer or the SD Card peripheral.

   

8. Perform the write operation in the other two SD cards by following steps 3 through 7 shown above.

9. Click Exit to close the Win32 Disk Imager.

   

You are now ready to setup the Raspberry Pi.

1. Perform the following steps:

   1. Insert the SD memory card into the Raspberry Pi.

   2. Connect the USB keyboard.

   3. Connect the HDMI display.

   4. Connect the Ethernet cable.

   5. Plug in the power cable.

   

   After a few moments, the monitor displays text, and the Raspberry Pi raspi-config configuration screen appears.

1. Press the up or down arrow key to select option 4, Internationalisation Options, and press Enter.

   

2. Press the up or down arrow key to select option I2, Change Timezone, and press Enter.

   

3. Press the up or down arrow key to select your country and press Enter.

   

4. Press the up or down arrow key to select the time zone in your country (if applicable) and press Enter.

   

5. Press the up or down arrow key to select option 8, Advanced Options, and press Enter.

   

6. Press the up or down arrow key to select option A2, Hostname, and press Enter.

   

7. Read the note and press Enter.

   

8. Enter the hostname as node1, node2, and node3 for the first, second, and third Raspberry Pi respectively and press Enter.

   

9. Press the left or right arrow key to select Finish and press Enter.

   

10. Press the left or right arrow key to select Yes and then press Enter to reboot the Raspberry Pi.

    

    The Raspberry Pi reboots.

    

    Notice the line that indicates the IP address of the Raspberry Pi.

11. Make a note of the the IP address. Perform the steps under Booting the Raspberry Pi and Configuring the Time Zone and Hostname in the other two Raspberry Pis (connected to the other two SD cards).

At this point, you can disconnect the HDMI monitor and the USB keyboard from the Raspberry Pi that is successfully setup.

Note: Do not disconnect the ethernet cable, power cable, and the SD card.

1. Start putty.exe and perform the following steps:

   1. On the boot screen, enter the IP address of the node1 Raspberry Pi in the IP address field.

   2. Enter node1 in the Saved Sessions field.

   3. Click Save.

   4. Perform steps a through c for the node2 and node3 Raspberry Pis.

   

   

2. Double-click node1 in the Saved Sessions list to SSH into node1.

   

3. Click Yes to accept the security alert.

   

4. Enter pi as the login name and raspberry as the password.

   

1. In a separate command-prompt window, enter ipconfig to get the netmask and default gateway for your network.

   

   Note: If you are using a wireless connection, the information appears under the Wireless LAN adapter heading.

2. In a PuTTY window, enter sudo nano /etc/network/interfaces and then perform the following steps:

   1. Comment out the iface eth0 inet manual line.

   2. Below that, add the iface eth0 inet static line.

   3. Use your network settings to add the IP, network, netmask, broadcast, and gateway addresses. For example:
      address 10.178.47.33 should be the IPv4 address alloted to the Raspberry Pi.
      network 10.178.47.0 should be the network prefix and zeroes.
      netmask 255.255.252.0 should match the subnet mask.
      broadcast 10.178.47.255 should be the network broadcast address.
      gateway 10.178.44.1 should match the default gateway.

      

      Note: You have to set the network properties to match the network configuration that you are using on your PC.

      

3. Press Ctrl + O and then press Enter to write the file.

   

4. Press Ctrl + X to close nano and return to the prompt.

5. Enter sudo reboot to reboot the Raspberry Pi and make the changes.

   

   Click OK to dismiss the Fatal Error prompt.

   

6. Start putty.exe again and connect to the node2 and node3 session. Perform steps 2 through 5 in the terminal for both the sessions.

   Note: Do not exit the node1 window.

You now have three PuTTY windows open and all of these windows have the session terminated due to the reboot command. Perform the following steps on all the nodes:

1. To reconnect to the Raspberry Pi, right-click in the header of the PuTTY window and select Restart Session.

   

2. Enter pi as the login name and raspberry as the password.

   

1. Launch the PSFTP tool and then perform the following steps:

   1. Enter open ipaddress.

   2. Enter pi as the login name and raspberry as the password.

   

   If a dialog box about a cached key is displayed, press Y to update the key.

2. Enter lcd C:\TEMP to change the local directory to the location of Oracle NoSQL Database.

   Note: In this example, the Oracle NoSQL Database is stored in the TEMP directory. You may change the local directory to where you have downloaded Oracle NoSQL Database.

   

3. Enter put kv-ce-3.2.5.zip.

   Note: Change the ZIP file name based on the version of the Oracle NoSQL Database you are using.

   

   This process may take several minutes because it uploads Oracle NoSQL Database setup file to the Raspberry Pi.

4. Type exit and press Enter to quit the PSFTP tool.

   

5. Repeat steps 1 through 4 in the other two nodes.

Perform the following steps on all the nodes.
Note: The screenshots below displays the output of the node1 only.

1. In the PuTTY window, enter unzip -q kv-ce-3.2.5.zip to extract Oracle NoSQL.

   

   Files are extracted inside the kv-3.2.5 folder. (The process may take several minutes.)

2. Enter mv kv-3.2.5 kvhome to rename the folder to kvhome.

   

Perform the following steps on ALL the nodes:

1. In the PuTTY window, enter sudo nano /etc/profile.d/env.sh. This creates a env.sh file in the /etc/profile.d directory.

   

2. Add the following content to the file:
   export KVHOME="/home/pi/kvhome" Sets the KVHOME variable. This directory holds the Oracle NoSQL Database.
   export KVROOT="/home/pi/kvroot" Sets the KVROOT variable. This directory holds the Oracle NoSQL Database data. If you wish to use an external drive for storing data, specify the path to the external drive in the KVROOT variable.

   

3. Press Ctrl + O and then press Enter to write the file.

   

4. Press Ctrl + X to close nano and return to the prompt.

5. Enter sudo nano /etc/hosts in the PuTTY window.

   

6. Add the following lines to the end of the file:
   <node1_ipaddress> node1 Replace the IP address with your node1 IP address
   <node2_ipaddress> node2 Replace the IP address with your node2 IP address
   <node3_ipaddress> node3 Replace the IP address with your node3 IP address

   

7. Press Ctrl + O and then press Enter to write the file.

8. Press Ctrl + X to close nano and return to the prompt.

9. Enter sudo reboot to reboot the Raspberry Pi and make the changes.

   

   Click OK to dismiss the Fatal Error prompt.

   

10. Wait for a few minutes and reconnect to the Raspberry Pi. To reconnect to the Raspberry Pi, right-click in the header of the PuTTY window and select Restart Session.

    

11. Enter pi as the login name and raspberry as the password.

    

1. Enter the following command to verify that Oracle NoSQL Database installed successfully:
   java -jar $KVHOME/lib/kvclient.jar

   

   The output displays the version of Oracle NoSQL Database that is installed on the Raspberry Pi. In this example, the 3.2.5 version of Oracle NoSQL Database is installed. You can verify the installation on all the nodes by following the same step.

Perform the following steps on ALL the nodes:

1. Enter the following command to open the ntp.conf file:
   sudo nano /etc/ntp.conf

   

2. Find lines starting with server and replace it with servers from pool.ntp.org, as shown in the screenshot below.

   

   

3. Press Ctrl + O and then press Enter to write the file.

4. Press Ctrl + X to close nano and return to the prompt.

5. Run the following command in the terminal to restart the ntp service:
   sudo /etc/init.d/ntp restart

   

6. Enter the date command to verify that the date is set as per the NTP server pool.

   

1. Create the KVROOT directory on ALL the hosts.

   mkdir $KVROOT

   

2. Run the makebootconfig command on ALL the hosts to create the configuration files:

   java -jar $KVHOME/lib/kvstore.jar makebootconfig \
   -host node1 -port 5000 -admin 5001 -root $KVROOT \
   -harange 5002,5010 -store-security none

   

   Change the host parameter to node2 and node3 when you run the makebootconfig command in the node2 and node3 terminal (as shown in the screenshot below).

   

   

3. Notice that a few configuration files have been created in the $KVROOT directory.

   ls $KVROOT

   

1. Start the SNA on ALL the hosts by executing the following command in the terminal:

   nohup java -jar $KVHOME/lib/kvstore.jar start -root $KVROOT&

   

   

   

   Note: Press Enter to regain control of the terminal.

   The SNA doesn't start automatically on boot. If you wish to start the SNA automatically on boot, you can add the nohup command to the /etc/profile.d/env.sh file for all the nodes.

2. Run the jps command to verify that the SNA has started.

   

   If you see kvstore.jar and ManagedService in the output, it means that the SNA and the Admin service has successfully started.

1. You can also verify that the SNA has successfully started, by using the ping command.

   java -jar $KVHOME/lib/kvstore.jar ping -host node1 -port 5000

   

   If you receive an output as shown in the screenshot, it means that the SNA is up and running. In this example, the node1 SNA is pinged. You can ping the SNA of other nodes by changing the host parameter.

1. Execute the runadmin utility to deploy the KVStore.

   java -jar $KVHOME/lib/kvstore.jar runadmin -port 5000 -host node1

   

2. The KV prompt opens. Now you will configure the store name. In the KV prompt, enter the following command:

   kv-> configure -name orcl

   

   Note: In the above example, the store name is set to orcl.

3. After configuring the store name, deploy a zone in the store. Enter the following command to deploy a zone:

   kv-> plan deploy-zone -name India -rf 3 -type primary -wait

   

   Note: The Replication Factor (RF) for zone India is set as 3 and the zone type is Primary.

4. Deploy the Storage Nodes and the Admin Services for the nodes. Run the following command in the KV prompt:

   kv-> plan deploy-sn -znname India -host node1 -port 5000 -wait
   kv-> plan deploy-admin -sn sn1 -port 5001 -wait
   kv-> plan deploy-sn -znname India -host node2 -port 5000 -wait
   kv-> plan deploy-admin -sn sn2 -port 5001 -wait
   kv-> plan deploy-sn -znname India -host node3 -port 5000 -wait
   

   

   The three Storage Nodes are deployed in the same zone along with the Admin Services. In the example, the SN3 is not configured as admin which means that the runadmin utility cannot be accessed by SN3.

5. Create a topology by using the existing (AllStorageNodes) pool. Enter the following command in the KV prompt:

   kv-> topology create -name 1x3 -pool AllStorageNodes -partitions 150

   

   Note: The name of the topology in the above example is 1x3.

6. Deploy the topology.

   kv-> plan deploy-topology -name 1x3 -wait

   

   After the command execution completes, you have an operational Oracle NoSQL cluser deployed.