These instructions install the bare minimum that is required to run the MaxScale system test setup. This configuration requires about 10GB of memory to run.
MDBCI is a tool written in Ruby programming language. In order to ease the deployment of the tool the AppImage distribution is provided. It allows to use MDBCI as a standalone executable. FUSE should be installed on all linux distributions as it's required to execute AppImage file.
- glibc >= 2.14
- fuse
- fuse-libs - additional fuse libraries for CentOS
- libfuse2 - additional fuse libraries for Ubuntu and Debian
Debian/Ubuntu:
sudo apt-get install -y libfuse2 fuse
CentOS/RHEL:
sudo yum install -y fuse-libs fuse
You also may need to add current user to the fuse
user group in case you are getting fuse: failed to open /dev/fuse: Permission denied
error.
sudo addgroup fuse
sudo usermod -a -G fuse $(whoami)
Check Troubleshooting section for additional help.
-
Download MDBCI:
sudo wget https://mdbe-ci-repo.mariadb.net/MDBCI/mdbci -O /usr/local/bin/mdbci && sudo chmod +x /usr/local/bin/mdbci
-
Run installing MDBCI dependencies:
mdbci setup-dependencies
-
Fill in the MDBCI configuration settings (for example, credentials of cloud platforms, private repositories, and etc.):
mdbci configure
You can follow the MDBCI configuration to read more about MDBCI configuration.
-
Log out and back in again. This needs to be done in order for the new groups to become active.
Most products to be installed on the machines require additional information to be stored on the MDBCI host. Run the following command to generate product repositories configuration files.
./mdbci generate-product-repositories
See generate-product-repositories command documentation for details.
To get configuration examples, use command:
mdbci deploy-examples
The following command will place confs
and scripts
directories into the current working directory.
In order to generate the configuration out of the sample template and create VMs run:
mdbci generate -t confs/libvirt.json my-setup
mdbci up my-setup
Once the last command finishes, you should have a working set of VMs in the my-setup
subfolder.
See also: