142
edits
Changes
Jump to navigation
Jump to search
==== Keycloak ====
Until all the required components are finished, A Keycloak server is be set up for authentication. After all the core features can be handled by the auth system, it will disappear again.
Already implemented: Allows the user to * Create a VPN client.(already implemented)Might be extended to allow users to * create their own isolated networks, and * invite people to them. ==== Shell ====Will allow users to* create shell accounts on a shared server* manage some static web space.
Add picture
[[File:Bitmask-login.png|thumb|right|The login view of the bitmask account manager]]
'''Bitmask''' is a Fork of the Zombi infrastructure. The reason for the fork was to provide a Platform where new aproaches can be tried out, without compromising the stability of the existing Zombi services. It is still tightly connected with the Zombi Platform, and thus shares some of the infrastructure.
* Only password-authentication is supported; Multi-Factor authentication can not be implemented, and neither can alternative login methods (such as key or certificate-based authentication).
* New attributes cannot easily be added to user accounts.
==== OAuth2 Service ====
Handled via shell scripts for now, will be handled via the user self-service endpoint.
=== Ressource Resource Mangement ===Some Ressources Resources are required for many projects, and should be easy for users to claim. ==== Git ====Version control is important, and so every user should have access to a namespace where they can add public and private repos.
==== VPN ====
==== Containers ====
Will allow users to
* run their own containers images on the shared infrastructure* Assign ressources
* View the logs
* exec into them
==== Subdomains ====
Will allow users to
* Create new subdomains that can be used for their services
==== Database ====
Handled via shell scripts for now. Will allow users to * create database access for own projects* export them ==== File Storage ====Will allow users to* reserve file system space for own projects* Add backup plans for data inside ==== Object Storage ====Will allow users to* create S3-Compatible storage on top of a created file storage claim* access them via a web interface ==== Private Docker registry ====Will allow users to* create namespaces to upload their images into* upload images ==== Mail ====Will allow users to* create outgoing SMTP service accounts for projects.* optionally create new mailing lists ==== Project CI/CD ====Using CI/CD to build projects should be supported, but here it is hard to implement permissions and export themaccess control.
==== Storage VMs ====Will allow users to :* create S3-Compatible storage an isolated VM for their projects, and access them.
