Follow

Installing the redborder Community Edition Manager

Requirements

redBorder is a software which has some minimum requirements in order to function correctly. The minimum essential elements required for installation as well as those recommended for correct performance are shown in the following table:

     Minimum Recommended
RAM 16 GB 32 GB
Processor 2 Cores 4 Cores
HD 24 GB 100 GB

Downloading the ISO

In order to download the ISO image, we must be registered. Once we are logged in to the redborder web, we must go to Community -> Downloads. On this page we will find all of the redborder editions along with their corresponding specifications and characteristics.

To download the Community edition, click on DOWNLOAD in the Community section.

Burning the ISO Image

The ISO image is prepared to perform the boot from a DVD reader, USB device or as an ISO file for a virtual machine.

In order to burn the ISO image from a Linux system to a USB device, the following command needs to be used if the USB device is mapped in /dev/sdd:

[root@machine ~]# dd if=redBorder-3.1.68-1-x86_64-6.5-community.iso of=/dev/sdd bs=10M

 

Installing the ISO

Once we have booted the redborder ISO, we will see the installation menu. To perform the installation, select the option: Install Community Manager:

Once in the installation process, the user only needs to confirm the installation destination and root password. redborder is prepared for unattended installations and so we should be especially careful with the time we have to respond to these three questions if we wish to modify the default options:

Once this page has been confirmed, the installation will carry out all of the necessary processes to prepare the system for configuration.

By default, the root password will be redborder.

Basic Configuration

Upon completing the installation process, we have two configuration options depending on whether or not there is a DHCP server.

  1. Dynamic IP (DHCP): in this case, redborder will have acquired an IP in its network interface and will have auto-configured in order to operate in said address.
  2. Static IP: in this case redborder will not have configured and we will have to access the system in order to perform the configuration. To gain access we will use the root user and the password we selected during the installation.

Once inside the system, we will start the configuration manager. To do this we will execute:

[root@rbmanager ~]# rb_sysconf

In the configuration we have several options:

To start the configuration we begin with option 1 - System configuration:

  • Option 1 - Hostname: we must enter the host name of the machine where redborder has been installed.
  • Option 2 - Set local time: allows us to indicate a local time for the system.
  • Options 3 y 4 let us configure parameters not included in this HOWTO.

Returning to the main menu, in option 2 - Network configuration we will have to configure everything related to the network environment:

  • In option 1 - Management Network configuration we will have the option of creating a link.

When we select the option n, we are asked for:

          - Insert bonding number [0] : The default value is "0" and indicates the link index (at redBorder we use redundant links called bonding).

          - Insert bonding first port [0] : The default value is "0" and allows us to indicate the network port index to use in the management link.

          - Insert second port (y/N) : If only one port is needed for management, use the default value "N".

          - Insert management IP address: We will enter the IP that we want to assign to redborder.

          - Insert management Netmask: We will enter the network mask that we want to assign to redborder.

          - Insert default gateway for this management interface (Y/n): Indicates whether or not we want to assign a link port to redborder. Por defecto indicaremos Y.

          - Insert default gateway []: We will enter the gateway IP address.

          - Insert a route for this bonding (y/N): Indicates whether or not we want to indicate a route for the link created. By default we will indicate "N".

Once the link is created, we return to the Management Network configuration menu and select:

  • option 2 - DNS and domain settings: in this option we will be asked to:

          - Insert Domain [redborder.cluster] : we are asked to enter the domain which redborder will be integrating.

          - Insert DNS Primary : we are asked for the DNS server to be used.

          - Insert DNS Secondary (optional) : we are asked for the secondary DNS server to be used. A secondary DNS server is not necessary by default. 

Once the previous steps have been completed, we must apply the configuration with the option a - apply.

Note: At this time we will see that several operations are executed. Please be patient because this process may be lengthy depending on the machine's hardware.

Returning to the main menu, we have option 3 -  Passwords. Within this option we can modify the different passwords used by default for the different users. Remember that the default password is redborder.

Lastly, we have option 4 - Backup system which is outside of the scope of this HOWTO.

Using redBorder

Once we have carried out all of the previously described configuration steps, we will be able to access the redborder web interface by entering the IP address of the machine where redborder has been installed in a web browser using the admin user and the administration password, which will either be the default password (redborder) or another entered previously in the configuration menu.

Basic Troubleshooting

To verify the correct functioning of redborder, we can access the system via ssh using root user and execute the command: 

[root@rbmanager ~]# rb_get_services.sh all
-----------------------------------------------
Service                 rbmanager         
-----------------------------------------------
chef-client:            running           
druid_coordinator:      running           
druid_realtime:         running           
druid_historical:       running           
druid_broker:           running           
kafka:                  running           
zookeeper:              running           
rb-monitor:             running           
rb-webui:               running           
rb-workers:             running           
memcached:              running           
erchef:                 running           
chef-solr:              running           
chef-expander:          running           
chef-server-webui:      not running       
bookshelf:              running           
rabbitmq:               running           
postgresql:             running           
nginx:                  running           
nprobe:                 running           
rb-sociald:             running           
aerospike:              not running       
--------------------------------------------------
Total:                  20                
--------------------------------------------------
Running: 20  /  Stopped: 2  /  Errors: 0  /  Unknown: 0

This command should show services in "running" status in green, and services in "not running" status in orange.

If at any time any of the two statuses are shown (running or not running) in red, it means that the service is in the opposite state of that shown. Example: if we see that a status appears as "running" in red, it indicates that the service is running but should be turned off. The same applies to the reverse case, if we see a "not running" status in red, it indicates that the service is not running but in fact should be.

 

Have more questions? Submit a request

Comments

Powered by Zendesk