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
Last updated