Portal

  • Why am I unable to connect to the portal?

    Check your credentials, are these credentials for this region? Are you using the right domain name?

  • What should I do if I get a “Connection Timeout” error?

    Verify that you are connecting from an authorized network or VPN Clear your browser cache and cookies Try accessing the portal using a different web browser

  • How do I reset my forgotten password? Contact your OpenStack administrator through the established support channels. For security reasons, password resets require verification of your identity and cannot be performed through self-service.

Instances

  • Why won’t my instance launch?

There are several common causes for instance launch failures:

  • Insufficient quota limits for CPU, RAM, or storage

  • Network connectivity issues in the selected availability zone

  • Invalid or incompatible image format

  • Resource constraints in the selected compute node

  • Why can’t I connect to my instance via SSH?

First verify these common configuration points:

  • Security group rules are properly configured to allow SSH traffic

  • The SSH key pair was correctly specified during instance launch

  • The instance has a valid floating IP address assigned

  • The instance’s operating system firewall allows SSH connections

  • How do I properly stop/start my instance?

When managing instance power states, it’s important to understand the different options available and their implications for both functionality and costs:

  • Shelving (Recommended for cost savings): The optimal choice when you need to temporarily decommission an instance while preserving its configuration. When you shelve an instance:

    • The instance state is saved to persistent storage
    • All compute resources are released, stopping associated charges
    • The only cost incurred is for the stored image
    • Perfect for instances you don’t need for extended periods but plan to use again

  • Standard Power Actions:

    • Soft shutdown (Stop): Sends a graceful shutdown signal to the operating system. Note that this still reserves compute resources and incurs charges
    • Hard shutdown (Power Off): Forces an immediate shutdown, which may cause data loss. Like soft shutdown, resources remain reserved
    • Pause: Temporarily freezes the instance state in memory, maintaining resource allocation and charges
    • Suspend: Saves the instance state to disk and frees up RAM, but still reserves compute resources

For cost optimization, always use shelving when you need to stop an instance for more than a few hours. Only use other power states when you need rapid instance availability or for brief maintenance windows.

Storage

  • Why is my volume creation failing?

Volume creation failures typically occur due to:

  • Exceeding your storage quota

  • Specifying an invalid volume size or type

  • Try to use a different volume type

  • How do I expand an existing volume?

Volumes can be expanded, but note that this process requires careful attention:

  • Ensure your instance is shut down before resizing
  • Use the OpenStack dashboard or CLI to extend the volume
  • After resizing, boot your instance and expand the filesystem
  • Be aware that volume shrinking is not supported

Quotas and Resource Management

  • Why am I receiving quota exceeded errors?

Quota management is essential for cloud resource allocation:

  • Review your current quota usage in the dashboard
  • Request quota increases through proper channels if needed
  • Consider cleaning up unused resources
  • Use flavor sizes that better match your workload requirements

Security

  • How do I ensure my instances are secure?

Implement these security best practices:

  • Regularly update operating system packages

  • Use strong passwords and key-based authentication

  • Implement the principle of least privilege in security groups

  • Enable only necessary ports and services

  • Monitor instance logs for suspicious activity

  • What should I do if I suspect a security breach?

If you suspect a security incident:

  • Immediately isolate the affected instances
  • Create snapshots for forensic analysis
  • Contact the security team and cloud administrators
  • Document all observations and actions taken

Maintenance and Updates

  • Will I be notified of planned maintenance?

Your cloud administrators will communicate:

  • Scheduled maintenance windows

  • Expected impact on services

  • Required actions from users

  • Emergency maintenance procedures

  • How do I prepare for planned maintenance?

Before scheduled maintenance:

  • Save all important work
  • Create backups of critical data
  • Document running workloads
  • Plan for potential service interruptions
  • Test your recovery procedures