Our clients all over the globe (US, Hong Kong, Singapore, Italy, Finland) have diverse needs which range from managing physical Linux server clusters with Foreman and Puppet to managing fully automated AWS-based Cloud infrastructures with Terraform, Puppet and Ansible.
Case 1: Linux HPC cluster automation
Our customer struggled in provisioning and maintaining their Linux HPC cluster manually. We stepped in and deployed Server Lifecycle Management with Foreman and Identity Management with FreeIPA. New nodes can now be provisioned quickly and easily at any time. Users can login to the cluster nodes using their Active Directory credentials. Changes can be made to all the nodes safely and effectively.
Case 2: Windows software robot automation project
Our customer needed a way to keep their Windows software robot instances consistent. They started an automation project based on Puppet and Powershell DSC. We helped them to get up to speed by providing best practices, training and by helping develop the actual automation code.
Case 3: Software / hardware startup
Our customer was growing and manual way of maintaining their growing install base was taking too much time and producing too many issues. We resolved this problem by separating production, staging and develoment Cloud infrastructures using Terraform and Puppet. They can now focus on their primary business, which is software development.
Case 4: Containerized Buildbot CI/CD system
Our customer used Buildbot to ensure that their software builds cleanly on more than dozen operating systems, including all major Linux and *BSD distributions and Windows. The old Buildbot environment was getting very outdated, so we rebuilt it from scratch. The new setup is based on Docker containers that are spun up on demand. We also included automated MSI packaging for Windows to make software releases trivial.
Case 5: Automating Jenkins configurations
Our customer was using Jenkins for continous integration and delivery. The setup had grown organically with manual modifications for some years and fear of breakage hindered changing the configuration. We stepped in and converted all the Jenkins configurations to infrastructure code, allow controlled changes to Jenkins without fear of breaking it.
Case 6: Keycloak domain mode cluster
Our customer wanted to migrate more and more of internal and SaaS services to Keycloak, but was worried about lack of high-availability in standalone Keycloak. We created a Keycloak domain mode cluster for them and integrated it with Prometheus monitoring system. This allowed the customer to start using Keycloak authentication for critical services like AWS and Slack - with help from us.