Denvr Cloud Docs
  • Welcome to Denvr AI Services Docs!
  • OVERVIEW
    • Getting started
      • Launch a virtual machine
      • Secure Shell (SSH): Best Practices
      • API Usage samples
      • Registration
    • Data centers
    • Shared responsibility model
    • Technical support
    • What's new!
  • PLATFORM
    • Dashboard
    • Applications
    • Virtual machines
    • Bare metal
    • Storage
    • Networking
    • User management
    • Billing
  • API Reference
    • Authentication
    • Clusters
    • Applications
    • Virtual machines
    • VPCs
  • Additional Information
    • FAQs
      • Desktop vs data center GPUs
      • Differences of bare metal and virtual machines
      • GPU monitoring
      • Using Github with SSH keys
      • Data persistence and recovery
      • Do you support Kubernetes?
      • Installing GPU drivers
      • What is the network bandwidth?
      • What ports are publicly accessible?
      • What is persistent local storage?
      • Adding DAS to /etc/fstab
      • Provisioning States
    • Policies
      • Terms of Service
      • Privacy Policy
      • Maintenance policy
Powered by GitBook
On this page
  1. Additional Information
  2. FAQs

Provisioning States

Virtual machine and application lifecycles explained

Across various Denvr services, resources will transition between multiple states during their lifecycle. In particular, applications and virtual machines can have the following status values:

  • PENDING - waiting to transition to another state

  • PENDING_RESOURCES - Denvr is allocating resources

  • PENDING_READINESS - resources have been allocated and we are waiting your application or virtual machine to come online.

  • ONLINE - your application or virtual machine has been provisioned and is online

  • OFFLINE - the resource has been stopped, but still exists

  • FAILED - an error has occurred, please contact support

These status codes are available from both the console UI or REST API.

Apart from persisted root volumes and additional storage, you are only billed during the PENDING_READINESS or ONLINE states.

How does PENDING_READINESS work?

Virtual machines and applications take time to boot after resources have been allocated. Our readiness check involves pinging port 22 on virtual machines, or a user defined readiness port for applications. How long a virtual machine or application takes to pass the readiness is dependent on your particular VM or application startup process. On our base images, this should only a few minutes. Common causes of long (or infinite) pending readiness periods include:

  • Corrupted `/etc/fstab` files which block the boot process. See "Adding DAS to /etc/fstab".

  • Incorrectly configured firewall (`ufw`) blocking ssh access

  • Addition of slow or failing init scripts

  • Applications that pull down large models or datasets prior to starting the service

PreviousAdding DAS to /etc/fstabNextPolicies

Last updated 9 days ago