CERNBox Charts

This section gives a brief of how CERNBox is functioning as a part of ScienceBox. Configuring and running CERNBox is a bit of a dauting task solely because of lot of microservices and satellite components running as a part of the deployment. This section hopes to simplify and make the understanding of CERNBox deployment much clearer.

The below architecture depicts the CERNBox deployment.

As seen in the architecture, in order to run CERNBox on kubernetes, there are many components involved:

• OCIS Proxy: Web Proxy provided by ownCloud to incoming requests to REVA services.
• OCIS IDP: OAuth provider by ownCloud - Backed by an LDAP Server.
• CERNBox Web: CERNBox Web component.
• Reva Services:
  • Storage Services: Public, User and Home services are the CERNBox storage services that interface with EOS.
  • Auth Service: Bearer service is the CERNBox authentication service.
• MariaDB: Database to store all the cernbox share information.

All of the above described elements run as a kubernetes pods (deployment/statefulset) and interact with each other via kubernetes service mechanism.