Quickstart Update 12th April

Ensure you have access from HOST machine(s) to:

The custom configuration below may not be needed depending on your host computer and you intended use of the MSactivator™. If you are just running the product for evaluation purpose or training, don’t worry too much about these at first.

In a production environment, these custom configuration may be mandatory to allow your setup to support a higher workload.

Create the mini lab: clone the quickstart git repository from Github, download and run the MSactivator™ from DockerHub.

Contact your sales representative to request for a trial license

Open https://localhost/ and connect with username ncroot and password ubiqube.

Browse to "Settings" in the left menu and upload the free trial license you received.

The mini lab comes with 2 Linux container (linux_me / 172.20.0.101 and linux_me_2 / 172.20.0.102) for experimentation.

Credentials for the Linux machine are:

In order to ease your discovery of MSactivator™, we are providing a script that will create the mini lab environment for you:

To create the mini lab environment, run the CLI command from where you have cloned the quickstart Github project:

docker compose exec msa-dev /usr/bin/create_mini_lab.sh

Browse: https://localhost/ and connect with username ncroot and password ubiqube.

After Login, Go to Profile tab and Edit Profile. Update new password for ncroot and do Logout.

Browse: https://localhost/ and connect with username ncroot and updated password in previous step.

This lab use case will show you in a simple way how you can use MSactivator™ to automate the configuration of iptables-based firewall policy on the Linux containers included in the mini lab.

The development of this use case is detailed in this guide: Firewall Policy Automation

You can use the guide to recreate the use case step by step or you may also directly run the use case with the workflow and microservices that are installed in the mini-lab.

For that, you’ll have to select the subtenant named "TYRELL CORPORATION," click on the link "Automation" on the left menu and select the tab "Workflows." The workflow to use is "Simple Firewall (Python)."

The quickstart repository is maintained on https://github.com/ubiqube/quickstart, the latest version is tagged as tags/MSA-2.8.13

If you are upgrading your MSactivator™, the best and easiest option is to remove your Quickstart git repository and use git clone to get the new version.

Starting from it’s version 2.2.0, the quickstart project provides a script upgrade.sh for taking care of possible upgrade actions such as recreate some volumes, execute some database specific updates, update the libraries,…​

Let’s say that you are running the version MSA-2.8.10, to upgrade to the version MSA-2.8.13 you need to follow these steps:

For each release of the MSactivator™, there is a tag that you can use if you need to install a specific version of the product.

To install a tagged version, you can checkout the tag and go to the install steps above.

For example, the CLI command below will checkout the quickstart for the release MSA-2.8.13.

git clone -b MSA-2.8.13 https://github.com/ubiqube/quickstart.git

The releases and tags are available here

The script install_libraries.sh is installed in the container msa_dev.

This script is designed to populate the libraries for a fresh install or to update your libraries with the latest version from Github.

In case of calling this script on an existing setup, it will take care of merging the code from the Github master branch into your local development branch. With the option -y, an automated merge will be attempted, without the option, the script will ask for user input.