Blazing iconBlazing

Deployment Lifecycle

Edit on GitHub

Understanding the deployment process from plan to production

Blazing Core Compose follows a structured deployment lifecycle: validate → plan → apply → monitor.

Lifecycle Overview

Plain Text

Phase 1: Validate

Local validation of YAML configuration.

Command

Bash

What It Checks

  1. YAML Syntax: Valid YAML structure
  2. Schema Compliance: Matches Core Compose v0.2.0 schema
  3. Feature Availability: Requested features are supported
  4. Policy Requirements: Org-level policies are met
  5. Control Satisfaction: Compliance controls can be satisfied

Sample Output

Plain Text

Validation Errors

Bash

Phase 2: Plan

Preview what will be deployed without actually deploying.

Command

Bash

What It Shows

  1. Provider Selection: Which providers will be used
  2. Region Allocation: Specific regions to be provisioned
  3. Resource Summary: CPU, memory, GPU, storage
  4. Cost Estimate: Monthly cost with variance
  5. Compliance Status: Controls met/unmet
  6. Placement Rationale: Why providers were chosen

Sample Output

Bash

Plan Options

Bash

Phase 3: Apply

Execute the deployment plan.

Command

Bash

What It Does

  1. Server-Side Orchestration: API runs placement algorithm
  2. Resource Provisioning: Creates compute nodes, IPs, storage
  3. Network Setup: Configures ingress/egress, TLS certificates
  4. Service Deployment: Deploys containers across regions
  5. Health Verification: Waits for readiness probes
  6. Audit Logging: Records deployment details

Sample Output

Bash

Apply Options

Bash

Phase 4: Monitor

Track deployed services.

Monitoring Commands

Bash

Sample Monitoring

Bash

Deployment States

| State | Description | Actions Available | |-------|-------------|-------------------| | draft | YAML loaded but not validated | validate, plan | | validated | Schema checks passed | plan, apply | | planning | Computing placement | wait | | provisioning | Creating infrastructure | wait, cancel | | deploying | Rolling out services | wait, watch | | healthy | All services running | scale, update, destroy | | degraded | Some replicas unhealthy | rollback, investigate | | failed | Deployment failed | retry, rollback |

Atomic Deployments

Blazing uses atomic deployments: all resources succeed or all fail.

Success Path

Plain Text

Failure Path

Plain Text

No partial deployments: Either everything works or nothing changes.

Update Deployments

Modify existing deployments with apply:

Bash

Rolling Updates

Updates are rolled out gradually:

Plain Text

Zero-Downtime Updates

Guaranteed zero downtime if:

  • min_replicas ≥ 2
  • Health checks configured
  • Gradual rollout (default)

Update Example

Bash

Rollback

Revert to previous deployment:

Bash

Automatic Rollback

Blazing automatically rolls back if:

  • Health checks fail
  • Deployment timeout exceeded
  • Critical error during apply

Deployment Comparison

Compare two deployments:

Bash

Sample Diff

DIFF

Best Practices

1. Always Validate First

Bash

2. Review Plans Carefully

Check:

  • Cost estimates
  • Region selection
  • Compliance status
  • Resource allocation

3. Use Staged Rollouts

Bash

4. Monitor After Deploy

Bash

Watch for errors in the first 5-10 minutes.

5. Tag Deployments

Bash

Makes rollback easier:

Bash

Next Steps