DOCSEARCHbyAlgolia
Submit Docs

Octos Cloud Documentation

website·Indexed 30 days ago

https://docs.octosinfra.com

Enterprise-grade cloud infrastructure purpose-built for the Indian market. Documentation covers provisioning virtual machines, software-defined networking with zero egress fees, block and object storage, and usage-based billing. Includes API guides for managing volumes and networks, security compliance, and deployment use cases for Docker Swarm, Traefik, Portainer, and Odoo.

Tokens
15.4K
Snippets
54
Records
120
Agent score
50%

What's inside Octos Cloud

  1. Retrieve global monitoring overview

    Get a high-level monitoring overview for your infrastructure using the Octos Infra API. This endpoint provides a global view of system health.
    curl -X GET "https://cloud.octosinfra.com/backend/api/monitoring/global" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

  2. Best practices for Octos Cloud HA deployments

    Follow these best practices to maximize the resilience of your Octos Cloud architecture:

    • Physical Isolation: Distribute Instances across different physical hypervisors where supported.
    • State Management: Use replicated persistent storage (e.g., Ceph) or constrain stateful workloads to specific nodes and implement regular backups.
    • Network Configuration: Configure Security Group rules to permit internal cluster communication across all nodes within the Virtual Network.

  3. Odoo ERP deployment architecture on Octos Cloud

    The Odoo deployment follows a layered architecture where user traffic is routed from DNS to a Public IP, then through a reverse proxy (Nginx or Traefik) to the Odoo Application container, which communicates with a backend PostgreSQL database.
    User → DNS (odoo.yourdomain.com)
       → Octos Cloud Public IP
         → Nginx / Traefik
           → Odoo App Container
             → PostgreSQL Database

  4. Octos Cloud platform capabilities and hardware specifications

    Octos Cloud provides enterprise-grade cloud infrastructure specifically for the Indian market, hosted in Tier-III+ data centers. The platform utilizes 4th-Gen AMD EPYC™ Genoa (Zen 4) processors with DDR5 memory. All provisioned resources are fully dedicated, meaning there is no shared tenancy, no CPU credit throttling, and no artificial IOPS caps.

    Key capabilities include:

    • Compute: Dedicated vCPU and RAM on latest-gen silicon.
    • Block Storage: NVMe SSDs utilizing Ceph replication.
    • Object Storage: S3-compatible storage with 2× deduplication.
    • Networking: Zero egress fees and zero bandwidth caps.
    • Uptime SLA: 99.982% guaranteed availability.

  5. Understand Portainer architecture in Docker Swarm

    Portainer is deployed as a two-part stack in a Docker Swarm cluster:

    1. Portainer Server: The central database and web UI. It must run exclusively on a manager instance.
    2. Portainer Agent: A global service that runs on every instance (both managers and workers) to collect data and transmit it to the server.

  6. Deploy Sophos XDR/EDR endpoint protection

    Sophos Intercept X with Extended Detection and Response (XDR) is available to protect virtual machine instances from malware and ransomware. Key capabilities include:

    • CryptoGuard: Detects unauthorized encryption and rolls back files.
    • Anti-Exploit Hardening: Blocks exploit techniques targeting unpatched software.
    • Threat Hunting: SQL-like syntax queries for running processes and connections.

  7. Octos Cloud platform capabilities

    Octos Cloud is a cloud management portal utilizing 4th-Gen AMD EPYC™ Genoa processors with DDR5 memory. Key performance and cost characteristics include:

    • No CPU credit throttling (sustained clock speeds).
    • No artificial IOPS caps on NVMe SSDs.
    • Zero egress fees for outbound data transfer.
    • No bandwidth caps on network links.

  8. Octos Cloud network cost model

    Octos Cloud implements a zero-egress pricing model with no bandwidth caps. There are no charges for:

    • Outbound data transfer to the internet.
    • Traffic between Instances on the same Virtual Network.
    • API requests to the management plane.
    • DNS query resolution.

  9. Octos Cloud compute hardware specifications

    All Octos Cloud Instances are powered by 4th-Gen AMD EPYC™ Genoa (Zen 4) processors. The architecture features DDR5 ECC memory with hardware-level error correction, NVMe PCIe Gen5 storage bus, and a 25Gbps baseline network per VM. The hypervisor uses dedicated resource partitioning to prevent 'noisy neighbor' effects and CPU throttling.

  10. Understand Octos Cloud usage-based billing

    Octos Cloud uses a transparent, usage-based billing model where resources are metered hourly. Key billing characteristics include:

    • Monthly Cap: Maximum of 672 hours per billing cycle.
    • Zero Cost Items: There are no charges for egress (outbound data transfer), bandwidth (no caps or throttling fees), or management plane API calls.

  11. Implement High Availability (HA) on Octos Cloud

    To ensure services remain accessible during component failures on Octos Cloud, eliminate single points of failure using the following architectural principles:

    1. Maintain Manager Node Quorum: Deploy an odd number of manager nodes (typically 3 or 5). This ensures the cluster remains operational if a single manager fails.
    2. Replicate Worker Nodes: Deploy service replicas across multiple worker nodes. Orchestrators (such as Docker Swarm or Kubernetes) will automatically reschedule tasks from a failed node to healthy ones.
    3. Dynamic Routing: Use a reverse proxy (e.g., Traefik) deployed on manager nodes to dynamically route traffic to healthy service endpoints.

  12. Create a manual snapshot of an Instance or volume

    To create a manual point-in-time snapshot of a disk:

    1. Navigate to the Snapshots tab of the specific Instance.
    2. Click Create Snapshot.
    3. Provide a descriptive name for the snapshot.
    4. Select the target disk (either the OS disk or an attached volume).
    5. Click Create.