QMCLOUD
  • What is QMCLOUD
  • Overview
    • Component Details
    • Security and RBAC
    • Dependencies
  • Architecture
  • Main features
  • Installation and Configuration
    • QMCLOUD SaaS
      • SaaS Registration
    • AWS Marketplace
    • Self-hosting
  • User Interface and Navigation
    • Main menu
    • Dashboard
    • General action buttons
    • Stack and Canvas
    • Stack Details
  • Getting started
    • Pre-requisites
    • Login to QMCLOUD
    • Create organization
    • Add Role
    • Add User
    • Add Components
    • Add Stack Profile
    • Add Workspace
    • Add Stack
    • Compose Infrastructure Using the Canvas
    • Add AWS Vpc
    • Add Subnets
    • Connect VPC and Subnets
    • Save Canvas State
    • Deploy the Infrastructure
  • AI Copilot
    • Example deployment using AI Copilot
    • AI Copilot pre-defined prompts
  • Additional resources
    • Explainer video
    • Short video on AI Copilot
    • Quick walkthrough videos
    • Walkthrough of deployment of AWS EKS
  • Examples
    • Deploy AWS Firewall and Networking with QMCLOUD
      • Application and landing zone components
      • List of landing zone components
      • Deployment steps
      • VPC configuration details
      • Routing configuration details
      • Firewall configuration
      • Additional components configuration
    • Securing applications in AWS using Palo Alto firewall
  • Templates
    • AWS Landing Zone
    • AWS EKS
    • Azure Web App
Powered by GitBook
On this page
  • Summary
  • Logical Components

Was this helpful?

Overview

This page provides an overview of QMCLOUD and the various components.

PreviousWhat is QMCLOUDNextComponent Details

Last updated 12 months ago

Was this helpful?

Summary

QMCLOUD allows a user to compose, edit, and deploy cloud infrastructure resources with minimal programming experience. Once a user initiates the deployment of the desired state, QMCLOUD generates the required code automatically on behalf of the user and uses a third-party software (Pulumi) to initiate the deployment of resources.

QMCLOUD stores various configuration details in its internal database about a stack and the cloud resources that are deployed including properties, connections, and state of deployment.

QMCLOUD currently relies on the external Pulumi service to store the current state of the cloud infrastructure resources. The state is a set of metadata about the infrastructure so that it can managed appropriately. Each stack (a unit of infrastructure) has its own state, and state is how QMCLOUD knows when and how to create, read, delete, or update cloud resources.

Note - Please refer to this link on what is Pulumi service, and its state and how it stores the metadata.

Logical Components

QMCLOUD consists of the following logical components:

  • Organization

  • Workspace

  • Stack, Stack group and Stack profile

  • Canvas

  • Users, Permissions, and Roles

The following diagram depicts the high-level structure and components of QMCLOUD and their relationships.

Diagram – QMCLOUD components and their relationships

https://www.pulumi.com/docs/intro/concepts/state/