BitScope Cluster Module Guide

BitScope Cluster modules are packed for shipping in custom designed packing crates. The crates are well padded and designed as "snug-fit" around the cluster module to ensure safe transit. Refer to this image when unpacking a module (notes these images are for large modules, small ones are similar):

This requires two people to lift the module out of its crate.

To remove the module:

Once the module is removed from the crate the use of the tool is optional. However, it is important that the module is not dropped or otherwise exposed to external shock so caution is required with lifting and/or relocating it.

The cluster module has an internal 52 port network switch.

The first 48 ports connect to 48 LAN cluster nodes. The other 2 ports are available to connect to external networks and/or inter-connect the subnets inside the cluster. When first commissioning the cluster module it is necessary to interconnect the switch to the cluster control manager.

To do this connect the supplied pigtail patch cable as follows:

This connects the cluster hub (white keystone) to one of the two uplink connections (blue keystone). The other blude keystone allows connection to the external LAN. There are two fibre connections (white keystones on the right). These are not provisioned in this module. However they may be used to connect fibre links instead of one or both copper links, if required.

The cluster manager bootstraps from a Micro SD Card located as shown:

Be sure this card is in place before powering the cluster module for the first time.

The cluster manager requires this image to be able to control the cluster. In addition to managing the control plane hardware, it provides DHCP/DNS and TFTP/PXE boot services to the module.

The cluster module is identified by its asset tag:

The TAG/ID appears on stickers applied to exterior and interior of the module. Ensure these tags are not removed or relocated. They are used to identify the module for service and support enquiries.

The cluster has three main components that must power on to bootstrap correctly:

Power is applied to all three immediately but the control plane (re)boots the nodes when the switch has completed its bootstrap sequence. The cluster manager controls the sequence. It is located at the rear of the module:

It is required to power up the cluster and manage use the control plane. The control plane drivers, cluster manager and self-test software is all located on the USB thumbdrive and/or the Micro SD card plugged into into the Raspberry Pi on the hub. The image uses Raspbian Lite and we recommend it be backed up before use.

The cluster manager is pre-configured to perform a power-on self test. The test confirms correct operation of the cluster control plane and the connected nodes in the cluster. This software runs on the cluster control hub.

The 60 nodes in each module are geographically identified by their control plane ID.

The control plane numbers nodes from 1 to 60. When a cluster module boots with the default image, the control plane enables all nodes in sequential order. When viewed from the right of the module, node 1 is at the top-left of the module with node 2 below it down the first control plane bus (BitBar), followed by the second bus up to the tenth at the rear of the module.

The MAC addresses table for the 60 nodes in each cluster are:

In addition to the nodes, the the network switch and the cluster manager at the rear of the modules are mapped as follows:

The cluster manager is supplied with a boot image on Micro SD card and a backup USB drive.

This image runs a series of self tests and bootstraps all nodes in the cluster. Its correct operation is predicated on the cluster network being configured correctly as described in Section 2.

The cluster manager default client image contains:

If the location where the cluster is commissioned has WiFi, the most convenient way into the cluster (initially) is via WiFi.

Remove the USB thumb drive plugged into the cluster manager. If there is Micro SD card in the hub, remove it as well and put it somewhere safe (it contains a backup of the image). Mount the USB thumb drive on an external Linux computer or another Raspberr Pi and edit this file:

/etc/wpa_supplicant/wpa_supplicant.conf

Replace the network clause with the ssid and psk of the local WiFi.

country=US
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
  ssid="client"
  psk="secret"
  priority=1
}

When done, unmount and replace the USB thumb drive in the cluster hub and power on the cluster.

You should then find the hub appears on your network.

When the cluster managed is accessible via the network, log in as:

Once logged in, the control plane can be manually configured and operated.

The cluster control plane is accessible via:

A set of python command line programs are installed on the cluster manager to enable access to the websocket interface. A separate set of command line utilities are available for remote use. These are not descrived in this document.

The cluster nodes can be built using any Model B form-factor Raspberry Pi.

Special Instructions:

Please give the import declaration to your forwarder together with the shipping documents. Your forwarder will need this for customs. Please submit the declaration at the first point of entry. The declaration has to be submitted directly to customs officials.