Installation and Upgrades
What are the prerequisites for installing the Brainspace 7.0 containerized environment?
Three or more Linux machines/VMs running a modern Linux distribution.
Docker installed on each machine.
Amazon Web Services Command Line Interface (AWS CLI) installed on each machine.
Amazon credentials for accessing Elastic Container Registry (ECR).
File shares setup for /data and /localdata.
File shares can be set up on the application host or in a separate NAS.
To learn details about the installation process, consult the Installation Guide.
Is an Implementation Guide available?
Yes. It is available on the Brainspace Documentation website.
Is there a new pre-install script that checks if the environment is ready for containerized BRS 7.0 to install or upgrade?
Yes. The pre-install script is integrated with the install scripts provided for the containerized deployment, simplifying the process.
What is the process for installing future patches and new releases in Brainspace 7.0?
Because Brainspace 7.0 decouples the backup/restore process from the software upgrade process, upgrades should take minutes, or even only seconds in some cases. Details describing packaging and delivery, new installations, and upgrades are available in the Installation Guide.
Can air-gapped and DMZ’d installations of Brainspace be upgraded to the containerized version?
Yes. Images for Brainspace software will be provided in the form of a TAR file or set of TAR files. Details are provided in Appendix A of the Brainspace Installation Guide.
Will I be required to install every Brainspace 7.0 patch?
No.
How will upgrades be provided and installed for on-prem environments?
Each release will result in properly versioned (major.minor.patch) images being pushed to ECR. Consistent with the way that Reveal distributes images to on-prem customers, customers will be provided with AWS IAM (Identity and Access Management) credentials so that they can access a specific ECR repository that houses officially released Docker images. For customers that have their own image registry, instructions will be provided for how to use Docker CLI to download images from our ECR repository and push them to their registry.
Details are available in the Installation Guide.
If I were to upgrade my existing Brainspace instance, why wouldn't a supported OS version, such as Red Hat 8/9, work?
The Brainspace application and the JDK used in Brainspace are packaged as RPMs and have numerous dependencies, meaning they will not install unless those specific dependencies are satisfied, including the version. More specifically, we build a custom Yum repository for RHEL/CentOS 7 that is not recognized on a RHEL 8/9 system. If you were to upgrade to either a newer Red Hat version or a different OS, your instance of Brainspace would no longer function properly.