Introduction & motivation

This repo is a fork of memsql/deployment-docker, customized for building the Skai KS base MemSQL image that is used for building the automation image for our local environments and testing environments on Jenkins. This process is comprised of (as of Dec 2022):

1. Starting a cluster-in-a-box memsql docker image.
2. Running several cucumbers to populate it with schemas, tables and data.
3. Committing the docker state and upload the image to an artifactory.

Then we can download the image in different automation jobs, start it and run tests that rely on the committed data.

Q: Aren't the default SingleStore scripts sufficient for this use case?
A: No, because they don't allow the retention of data after having populated the image with data and committed it. Additionally, with the image built by the default scripts, it's impossible to start the image twice (i.e. start the committed image), due to the usage of the sdb-toolbox tool in the startup script.

For more information, read the original readme.

Differences with source repo

The main changes made to the repo are:

• Makefile: Explicitly specify our desired memsql version.
• Dockerfile-ciab:
  • Specify the base image and other tool versions.
  • Add permissions to run installations on the image.
  • Skip the VOLUME command, presumably to allow data retention on the image once we use it in our Jenkins automations.
• Startup:
  • Unregister host, as it prevents the committed image to be started again as a new docker in automation jobs.
  • Add custom memsql variable values to reduce the final committed image size.

Building the base image

Run the release job: https://jenkins-prod-microcosm.internalk.com/job/memsql-base-automation-image-builder-release. If you've made changes to the DSL files, you will need to run https://jenkins-prod-microcosm.internalk.com/job/memsql-base-automation-image-builder-main-dsl/ first.

Recommendations - discovery for next version upgrade

When it's time to upgrade from 7.6 to some new version, one of the steps will be to create a new base image for Skai's automation environment.

I suggest trying it like this:

1. Check what changes have been made on SingleStore's deployment-docker scripts repository since the version we forked.
   2 methods for doing that:
   • Via Github: https://github.com/kenshoo/memsql-base-automation-image-builder/compare/master...memsql:deployment-docker:master
   • Locally:
     1. git checkout this repo.
     2. git remote add -f memsql_src git@github.com:memsql/deployment-docker.git
     3. git remote update
     4. git diff master remotes/memsql_src/master
     5. git remote rm memsql_src If they seem necessary, apply them to the repo on your local machine.
2. Try to apply the same changes that PR #1 contains (see description for summary) to the current version of the official repo. Adjust version numbers accordingly.
3. If the repo has changed so much that this PR's changes are no longer applicable, know that the main changes were skipping the 'VOLUME' command, and running sdb-toolbox-config unregister-host. All the others were workarounds to issues we ran into.
4. Good luck!