Skip to main content

Cloud infrastructure

🌟 Status: Live on Mainnet

NodeOps Cloud makes it easy to manage Cloud infrastructure by letting developers use simple YAML templates to automate deployments.

This template-based approach allows you to define and consume Compute infrastructure in a declarative manner: enabling automation of your infrastructure deployments.

This allows you to consume and create infrastructure templates that enable:

  • Version control
  • Automated testing
  • Continuous integration and deployment
  • Modularity and reusability

Templates for developers​

NodeOps Cloud Compute is consumed via "playbooks" of standardized templates.

You may either:

Monetize your templates

In the boostrapping phase of the Network, templates earn 20% of the workload fee.

This allows early template contributors to enjoy a significant incentive should their template prove popular.

Templates for users​

Logged into the Cloud Marketplace, navigate to Deploy Templates.

Select from the NodeOps Network's public template marketplace

See the Get Started for detailed template setup steps.

The rationale for YAML templates​

NodeOps Cloud's "Infrastructure as Configuration" approach uses a YAML file, a data serialization standard commonly used for configuration files.

Using YAML templates for infrastructure provisioning offers several advantages:

  • Readability: YAML's simple syntax is easy for people and machines to understand

  • Declarative approach: Define the desired state of your infrastructure without specifying the step-by-step process to achieve it

  • Reusability: Templates can be parameterized and shared across multiple pipelines, reducing code duplication

  • Consistency: Standardized templates ensure that infrastructure is deployed consistently across different environments

These YAML templates are an effective solution for managing complex Cloud infrastructures: combining the power of automation with the simplicity and readability of declarative configurations.

Unit of consumption​

Each template playbook will provision your Compute infrastructure according to your use case and is charged according to the workload, measured as the Compute consumed. The Compute consumed is defined by Compute Units or CUs:

One CU is defined as:

1CU = 1 vCPU, 2GB RAM, 30GB NVMe Disk

What next?​