Welcome to the meshStack Documentation!
meshStack is the name of our technology that powers the meshcloud solution. This document is targeted at cloud architects and SREs and introduces the components of meshStack and their interaction.
It is a modular software platform solution that connects organizational processes like project and access management with cloud technology. It provides a unified administration interface to the organization while replicating configuration into attached cloud platforms.
It is NOT a meta-layer across clouds. Users access native cloud APIs for their deployments, but meshStack helps them to ensure a proper and common configuration across cloud technologies with additional functionality such as metering, billing, surveillance and others.
Integrating a cloud platform with meshStack generally consists of these steps:
- prepare the cloud platform for integration (Service Accounts, Identity Federation)
- configure & register the platform in meshStack
- provide Landing Zone implementations
- configure Metering & Billing
Please review the detailed documentation for each cloud platform type in the sidebar for more details.
meshModel mapping to Cloud Platform Concepts
Different Cloud technologies often introduce their own terms for similiar technological principles. In order to match them against each other and also show how this namings and technologies map to meshcloud's terminology of business entities. These mappings can be customized. For more details, please consult documentation of the platforms.
The connections are shown in the following matrix table:
|OpenStack||Domain (optional)||Project||Keystone Shadow User||Quota|
|Cloud Foundry||Organization||Space||UAA User||Quota|
|AWS||-||Account||IAM Role||CF StackSets / Organization Units|
|Azure||-||Subscription||AAD User||Blueprints / Management Groups|
|GCP||-||Project||GCD User||Organization Policy / GDM Template|
meshcloud will typically operate your meshStack installation as a managed service for you. As a managed service, all configuration and validation is done by meshcloud. Nonetheless, we make references to configuration options in the documentation so that operators get a better understanding of meshStack's capabilities. The configuration references also simplify examples and communicate the exact parameters that may need to be supplied by platform operators (e.g. Service Principal credentials).
meshcloud configures your meshStack installation using a dhall configuration model. As part of meshcloud's managed service, customers get access to their configuration in a git repository. This is also useful to communicate configuration options and track changes.
The configuration documentation will occasionally also make references to YAML configuration options. These will be replaced with
dhall models in the next releases. Dhall models can generate YAML configuration files dynamically, but provide superior features in terms of flexibility and validation.