From HollaEx Kit 1.4.2 To 1.5

This update contains the announcement plugin support, more flexibility at the color customizing, user note (memo), trading fee adjustment per user, Vault plugin batching interval customization support, general bug fixes and increased stability.

Please check the changelog for more information on these changes.

Pulling the latest HollaEx Kit

HollaEx Kit relies on Git for managing and hosting code and supports Git commands for managing your repo for the new updates. git pull origin master is pretty much the entire process for updating your kit. Follow this guide to avoid code conflicts and making sure that the update goes as expected.

Committing changes

git add -A && git commit -m "my-commit-message"

Before starting, commit and changes you've made to your kit.

Checking the Git Remote

git remote -v

You always should check your Git Remote URL for your HollaEx Kit before pulling it. If the result is you can proceed to the next step.

But If it's pointing a different repository, You should set it to point Official HollaEx Kit repo first, before pulling it. You can set the remote repo by using the command below.

git remote set-url origin https://github.com/bitholla/hollaex-kit.git

Pulling the latest Kit

git pull origin master

This command will pull the latest Kit from GitHub. Current latest version is v1.3.

If you changed the Git Remote URL by using git remote set-url, you should revoke it to the old one at this step. Use git remote set-url <YOUR_GIT_REPO_URL> first, before proceed.

New Settings Values

There are new values added on /settings for the brand-new features coming with the HollaEx Kit v1.5 and HollaEx CLI v1.11.

  • Custom resource requests / limits control on Kubernetes

ENVIRONMENT_KUBERNETES_API_CPU_LIMITS=500m
ENVIRONMENT_KUBERNETES_API_MEMORY_LIMITS=1024Mi
ENVIRONMENT_KUBERNETES_API_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_API_MEMORY_REQUESTS=1024Mi
ENVIRONMENT_KUBERNETES_STREAM_CPU_LIMITS=500m
ENVIRONMENT_KUBERNETES_STREAM_MEMORY_LIMITS=512Mi
ENVIRONMENT_KUBERNETES_STREAM_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_STREAM_MEMORY_REQUESTS=128Mi
ENVIRONMENT_KUBERNETES_PLUGINS_CPU_LIMITS=500m
ENVIRONMENT_KUBERNETES_PLUGINS_MEMORY_LIMITS=512Mi
ENVIRONMENT_KUBERNETES_PLUGINS_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_PLUGINS_MEMORY_REQUESTS=128Mi
ENVIRONMENT_KUBERNETES_ENGINE_CPU_LIMITS=500m
ENVIRONMENT_KUBERNETES_ENGINE_MEMORY_LIMITS=1024Mi
ENVIRONMENT_KUBERNETES_ENGINE_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_ENGINE_MEMORY_REQUESTS=128Mi
ENVIRONMENT_KUBERNETES_POSTGRESQL_CPU_LIMITS=100m
ENVIRONMENT_KUBERNETES_POSTGRESQL_MEMORY_LIMITS=200Mi
ENVIRONMENT_KUBERNETES_POSTGRESQL_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_POSTGRESQL_MEMORY_REQUESTS=100Mi
ENVIRONMENT_KUBERNETES_REDIS_CPU_LIMITS=100m
ENVIRONMENT_KUBERNETES_REDIS_MEMORY_LIMITS=200Mi
ENVIRONMENT_KUBERNETES_REDIS_CPU_REQUESTS=10m
ENVIRONMENT_KUBERNETES_REDIS_MEMORY_REQUESTS=100Mi
ENVIRONMENT_KUBERNETES_INFLUXDB_CPU_LIMITS=200m
ENVIRONMENT_KUBERNETES_INFLUXDB_MEMORY_LIMITS=400Mi
ENVIRONMENT_KUBERNETES_INFLUXDB_CPU_REQUESTS=100m
ENVIRONMENT_KUBERNETES_INFLUXDB_MEMORY_REQUESTS=256Mi

It is now possible to allocate exact amount of resources to HollaEx Pods on Kubernetes. Modify the values and running hollaex upgrade would override your existing resource allocation settings.

  • PostgreSQL database backup Cronjob with AWS S3 for Kubernetes

# Configmap
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_RULE='0 1 * * *'
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_REGION=
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_BUCKET=
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_TIMEZONE=
# Secret
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_ACCESSKEY=
ENVIRONMENT_KUBERNETES_S3_BACKUP_CRONJOB_SECRETKEY=

HollaEx CLI now provides a build-in Cronjob for Kubernetes to run periodical database backup and store it on AWS S3 bucket. Simply fill up the values above and run hollaex toolbox --set_backup_cronjob --kube would set the Cronjob on your Kubernetes Cluster.

The CLI will also creates the Cronjob while on hollaex setup automatically, if the values are fulfilled.

Resolving conflicts

You might face some conflicts due to the changes you made on your HollaEx Kit, including settings files configurations. Fix the conflicts through your code editor. You will most likely face conflicts at the settings files (/settings directory).

If the sensitive values (passwords) are causing conflicts, please make sure to accept the current values to keep the existing passwords.

Depends on user's setup and configurations, the part causing conflicts could be different. Please review them all clearly, and solve the conflict.

Upgrading HollaEx Core

bash install.sh

To upgrade the CLI manually to the latest version, simply run the CLI installer at your HollaEx Kit directory. The latest CLI should be v1.11.x.

hollaex upgrade

The upgrade command would bring your HollaEx Core version to the latest v1.24.0.

Follow the upgrade process with the CLI. Once it's all done, you'll be able to see the new HollaEx Core version number has been changed at /v1/health API endpoint. You could also use hollaex status command to check the status briefly.

Troubleshooting

If something went wrong, you can ask questions at bitHolla Forum with printed error logs to get a community's help.