Overview

The below process explains how QA should test a Gamma environment on KC-BRAINware5, KC-BRAINware25, and KC-BRAINware50 server units. This process will require two separate machines: personal laptop running linux or Mac OS and the KC-BRAINware hardware running the latest available ISO file.

Process

Personal Laptop Installation

This process will NOT work with Windows machines

  1. Install ruby v2.4.1 on your machine
  2. Install nebula gem
  3. Run nebula update creds
    • Will include the credentials to use inside an email attachment
  4. Run nebula update cli
  5. Run nebula config set env=gamma
    • This will change your environment to Gamma for license generation
  6. Run nebula license generate
    • Should get successful license with -gamma tag at the end
  7. Repeat above step until the necessary amount of licenses has been created

KC-BRAINware Installation

Changing KC-BRAINware environment to Gamma

  1. SSH into KC-BRAINware hardware using below credentials
    • username – Kramer
    • password – KC_Brainware
      • You could also connect keyboard, mouse, and display to KC-BRAINware hardware to change environment
  2. Run kramer config set env=gamma
    • This will show a message indicating a proper change in environment

License transfer from personal laptop to KC-BRAINware

Once licenses are generated you will need to send the licenses from your laptop to the KC-BRAINware unit

  1. Locate license files on the personal laptop
    • ~/.nebula/licenses
  2. Move the licenses from local machine to KC-BRAINware hardware
    • _scp *.gamma kramer@ip_of_hardware:~/.nebula/licenses
  3. Confirm licenses have been moved by the 100% indicator in your terminal

Configuring IP range

Once the licenses have been successfully moved to the KC-BRAINware unit, you will want to identify the IP range available on the local network for the necessary hosts for testing

  • KC5 – 5 hosts
    • Example = 192.168.1.1/29
  • KC25 – 25 hosts
    • Example = 192.168.1.0/27
  • KC50 – 50 hosts
    • Example = 192.168.1.0/26

Due to CIDR requirements, the IT administrator will have to segment a portion of the Network for the amount of hosts listed above. The values entered into the Kramer config are for more hosts than necessary, but this is due to CIDR limitations.

  1. Run kramer config set docker.brain.network.ip_range=
    • Enter IP value after the equals sign using the examples above for host numbers

Starting Gamma Brains

  1. Run kramer docker pull brain
  2. Run kramer docker update brain

Brains should start after the update process is finished.

Revision: 1
Last modified: 10 June 2020

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment