Cloud Installation
Warning
Cloud installation is no longer recommended. Please use the ISO image to install, refer to the On Premise Installation section.
Note
This section describes installation on a cloud server, if you would like to install on premise, refer to the On Premise Installation section.
Overview
Baruwa Enterprise Edition can be installed on a cloud server. At the moment the following cloud providers are supported.
The cloud installation system is based on Vagrant. You need to have vagrant installed on your local system to be able to provision a Baruwa Enterprise Edition system to one of these cloud providers. Vagrant provides installers for all major operating systems. Please refer to their site to download the installer for your operating system.
Of course you will need to create an account with your prefered cloud provider and signup for an API key.
You also require the Vagrant plugin for the cloud provider that you want to use installed.
Rimuhosting
To install the Rimuhosting Vagrant plugin, run:
vagrant plugin install vagrant-rimu
Vultr
To install the Vultr Vagrant plugin, run:
vagrant plugin install vagrant-vultr
DigitalOcean
To install the DigitalOcean Vagrant plugin, run:
vagrant plugin install vagrant-digitalocean
Linode
To install the Linode Vagrant plugin, run:
vagrant plugin install vagrant-linode
Installation
Once you have downloaded and installed Vagrant and the plugin you need to clone the Baruwa Enterprise Edition Vagrant files to your system:
git clone https://github.com/akissa/baruwa-vagrant.git
The above command should create a baruwa-vagrant directory, you need to change into that directory to issue the commands that follow.:
cd baruwa-vagrant
Configuration is by use of environment variables. You should export the variable to the environment to set them.
Rimuhosting
The following variables are required.
- RIMUHOSTING_APIKEY - The Rimuhosting API Key
- BARUWA_HOSTNAME - The hostname to assign to the server
- BARUWA_ACTIVATION_KEY - The Baruwa Enterprise Edition Activation Key
- BARUWA_PROFILE - The System Profile to setup options are
standalone,web,node,indexer,mq,backend,db,cache
The following variables are optional.
- RIMUHOSTING_DISK1 - defaults to 20GB
- RIMUHOSTING_REGION - defaults to DCDALLAS, the Dallas DC
- RIMUHOSTING_SIZE - defaults to 4GB
Additional variables are available and you can review those in the plugin documentation at https://github.com/akissa/vagrant-rimu
Generate an SSH key pair for use by the plugin.:
ssh-keygen -t rsa -b 4096 -f ~/.ssh/rimuhosting_rsa
After generating the ssh key pair, you should run the following command to setup the VPS.:
export RIMUHOSTING_APIKEY="rimuhosting apikey"
export BARUWA_HOSTNAME="baruwa.example.com"
export BARUWA_ACTIVATION_KEY="key"
export BARUWA_PROFILE="standalone"
vagrant up --provider=rimu
After the VPS has been setup you can login and proceed with configuration.:
vagrant ssh
Vultr
The following variables are required.
- VULTR_TOKEN - The API token
- BARUWA_HOSTNAME - The hostname to assign to the server
- BARUWA_ACTIVATION_KEY - The Baruwa Enterprise Edition Activation Key
- BARUWA_PROFILE - The System Profile to setup options are
standalone,web,node,indexer,mq,backend,db,cache
The following variables are optional.
- VULTR_REGION - defaults to Frankfurt
- VULTR_SIZE - defaults to “4096 MB RAM,90 GB SSD,4.00 TB BW”
Generate an SSH key pair for use by the plugin.:
ssh-keygen -t rsa -b 4096 -f ~/.ssh/vultr_rsa
After generating the ssh key pair, you should run the following command to setup the VPS.:
export VULTR_TOKEN="vultr token"
export BARUWA_HOSTNAME="baruwa.example.com"
export BARUWA_ACTIVATION_KEY="key"
export BARUWA_PROFILE="standalone"
vagrant up --provider=vultr
After the VPS has been setup you can login and proceed with configuration.:
vagrant ssh
DigitalOcean
The following variables are required.
- DIGITAL_OCEAN_TOKEN - The API token
- BARUWA_HOSTNAME - The hostname to assign to the server
- BARUWA_ACTIVATION_KEY - The Baruwa Enterprise Edition Activation Key
- BARUWA_PROFILE - The System Profile to setup options are
standalone,web,node,indexer,mq,backend,db,cache
The following variables are optional.
- DIGITAL_OCEAN_REGION - defaults to Frankfurt 1
- DIGITAL_OCEAN_SIZE - defaults to 4GB
- DIGITAL_OCEAN_PRIVATE_NET - defaults to false
Additional variables are available and you can review those in the plugin documentation at https://github.com/smdahlen/vagrant-digitalocean
Generate an SSH key pair for use by the plugin.:
ssh-keygen -t rsa -b 4096 -f ~/.ssh/digital_ocean_rsa
After generating the ssh key pair, you should run the following command to setup the VPS.:
export DIGITAL_OCEAN_TOKEN="digitalocean token"
export BARUWA_HOSTNAME="baruwa.example.com"
export BARUWA_ACTIVATION_KEY="key"
export BARUWA_PROFILE="standalone"
vagrant up --provider=digital_ocean
After the VPS has been setup you can login and proceed with configuration.:
vagrant ssh
Linode
The following variables are required.
- LINODE_TOKEN - The Linode API Token
- BARUWA_HOSTNAME - The hostname to assign to the server
- BARUWA_ACTIVATION_KEY - The Baruwa Enterprise Edition Activation Key
- BARUWA_PROFILE - The System Profile to setup options are
standalone,web,node,indexer,mq,backend,db,cache
The following variables are optional.
- LINODE_REGION - defaults to frankfurt
- LINODE_SIZE - defaults to 4096
- LINODE_LABEL - defaults to baruwa-enterprise-edition-vagrant
Additional variables are available and you can review those in the plugin documentation at https://github.com/displague/vagrant-linode
Generate an SSH key pair for use by the plugin.:
ssh-keygen -t rsa -b 4096 -f ~/.ssh/linode_rsa
After generating the ssh key pair, you should run the following command to setup the VPS.:
export LINODE_TOKEN="linode token"
export BARUWA_HOSTNAME="baruwa.example.com"
export BARUWA_ACTIVATION_KEY="key"
export BARUWA_PROFILE="standalone"
vagrant up --provider=linode
After the VPS has been setup you can login and proceed with configuration.:
vagrant ssh
Configuration
After the VPS has been setup and converted you can now run baruwa-setup to complete configuration. Refer to the Configuration section for details