First of all: This is not supported by IBM and also not intended for a production environment!
Orient Me 220.127.116.11 does not run on a 4 core virtual machine which means that I’m not able to run it locally on my notebook. Therefore I searched for a solution to downgrade Orient Me to be able to install it locally. Thanks to Ben who also blogged about this.
Below you will find instructions how to install a smaller deployment based on Orient Me 18.104.22.168. You can also use the customized yml files to downsize an already installed environment (just compare them against your deployment).
Please download the customized yml files here. You will need them to deploy the custom installation.
- Deploy CfC based on the official documentation
- Create PVs and PVCs based on the official documentation (optional: only one volume is needed for Solr and Zookeeper)
- Execute microservices/hybridcloud/bin/install-supplemental.sh
- Execute microservices/hybridcloud/bin/setup.sh -fs
- Customize configmap (kubectl edit configmap) and remove all zookeeper nodes except “zookeeper1:2181”
- Execute microservices/hybridcloud/bin/mongo.sh
- Execute custom ymls:
kubectl apply -f 1-zookeeper.yml
kubectl apply -f 2-solr.yml
kubectl apply -f 3-haproxy.yml
kubectl apply -f 4-redis.yml
kubectl apply -f 5-orientme.yml
After finishing these steps you will have a working Orient Me installation with one instance for every microservice. Only MongoDB will be deployed using the original script because I had some issues after downsizing it. I will dig deeper into the MongoDB configuration to hopefully find a solution for this too.
Once again: Not supported. Not for production environments.