This month, we worked towards a proof of concept OpenAppStack cluster with some applications deployed to them and integrated with a Single Sign-On (SSO) server and a web proxy. Additionally, we have worked on the design document that explains how applications will be installed and updated in OAS.
Proof of concept
Last month we chose to use Kubernetes for installing and managing OpenAppStack applications. Therefore, this month the team set up development Kubernetes clusters and started installing applications to them. This enables us to develop a proof-of-concept of OpenAppStack that runs some applications integrated with a proxy and SSO server. We are trying to automate these installations as much as possible, however we are not focusing on auto-updating or auto-installation yet.
Like we hoped, some applications were relatively easy to install, because they have helm charts available in the official Helm repository. On the other hand, we have also already run into some issues with applications that were a bit harder to set up, like the SSO server.
Because part of our team spent most of their time on finishing development work for the Totem project, we could not spend as much time on the proof of concept as we wanted. However, we hope to be able to show you something at the OTF summit this month!
It is important to be able to explain the setup we envision for the people interested in the project on a whole, as well as developers planning to work on the project. Our current documentation focuses mostly on the design of the application cluster and how applications can be made compatible with OpenAppStack. We will iteratively develop this documentation, but a first version of it can be found on our website