This chapter describes the design concepts of Blunix Stack and how it aims to provide a stable, predictably priced, easy to manage and fully automated managed hosting environment.
The cloud provider account is provided by the customer of Blunix GmbH. We do not provide any servers, cloud instances or appliances. We only manage Debian Linux installations.
You own your infrastructure, we just maintain it and give you the configuration management code for doing that.
Hostnames and groups¶
The naming of servers and server groups are as follows:
|Naming scheme abbreviation
|Name of the company
|Logical name for a group of servers
|Point in development process the group is allocated for
|Central log server
|Number of servers that exist with this configuration
Naming scheme examples:
|Customer GmbH's utility stack production central log server one
|Customers GmbH's "myapp" project staging web server one
|Example GmbH's (a customer of Customer GmbH)"wiki" project production web server two
|Customer GmbH's "myapp" project production load balancer - redundant instance one (active)
|Customer GmbH's "myapp" project production load balancer - redundant instance two (failover)
As well as for groups of servers:
|Customer GmbH's utility stack production
|Customer GmbH's "myapp" project production
Domains are split into three categories:
- Public domain: (your-company.com)
- Private internal domain: (cus.int) only reachable over company VPN (monitoring.cus.int, jenkins.cus.int)
- Public internal domain: (cus.pub) reachable over regular internet (Example: public-staging.cus.pub)
All domains have to be hosted with a DNS provider has certbot dns challange plugin for generating Letsencrypt certificates.
All Debian installations run dnscrypt-proxy which resolves all internal domains.
Each Debian installation runs a firewall (shorewall) that has a whitelist for incoming and outgoing connections on all network interfaces.
The firewall solution provided by the cloud provider is not used.
Each Debian installation is part of an end-to-end encrypted mesh VPN using wireguard.
The internal network or subnet solution provided by the cloud provider is not used.
The employee VPN realized with wireguard allows for fine grained access control to the infrastructures services. When connected to the VPN, employees can resolve internal Domains (Example: cus.int - backup.cus.int).
Blunix encourages the use of Letsencrypt certificates for all your