Skip to content

User Guides: Skyline Dashboard

This section provides brief walkthroughs for common tasks in Tier5.

Accessing the Dashboard

To access the Skyline dashboard, you will need to log in.

Login Page

  • Region: Select RegionOne. This is currently the only available region.
  • Domain:
    • default: Use this for private (hosted or on-premise) clouds.
    • [Specific Domain]: If you are in a shared cloud environment, enter your assigned domain.
  • Username / Password: Enter your provided credentials.
    • Users outside the default domain must use the <username>@<domain> format.

Dashboard Overview

Once logged in, you will see the main dashboard overview.

Skyline Dashboard Overview

Managing Compute (Nova)

Launching an Instance

  1. Navigate to Compute → Instances: Instances List

    • This view shows all your running virtual machines, their internal/floating IPs, and power state.
  2. Click Launch Instance: Launch Instance Wizard - Details

    • Instance Name: Give your VM a unique name.
    • Availability Zone: Select the zone (e.g., nova).
    • Count: Launch multiple identical instances at once if needed.
  3. Select the Boot Source: Launch Instance Wizard - Source

    • Image: Boot from a pre-uploaded OS image (e.g., Ubuntu, CentOS).
    • Volume: Boot from a persistent block storage volume.
    • Volume Size: Define the size of the root disk.
    • Delete on Terminate: Checked by default for ephemeral root disks. Uncheck if you want the volume to persist/survive after the instance is deleted.
  4. Select the Flavor:

    • Flavors define the compute capacity (vCPU, RAM, Disk).
    • Choose a flavor that matches your workload requirements.
  5. Configure Networking: Launch Instance Wizard - Networking

    • Select the private network(s) to attach to the instance.

    Launch Instance Wizard - Security Groups * Security Groups: Assign firewall rules (e.g., default, ssh-web).

  6. System Configuration: Launch Instance Wizard - Key Pair

    • Key Pair: Select an SSH key pair for secure access.
  7. Review and Launch: Launch Instance Wizard - Overview

    • Click Launch Instance to start the provisioning process.

    Instance Spawning

    • The status will change from Build to Active once ready.

    Instance Active

Resizing an Instance

If your workload increases, you can resize the instance to a larger flavor.

  • Ensure the VM is powered off for safe resizing (recommended).
  • Select Resize Instance from the actions menu.

Managing Images

  • Images: View available base OS images. Images List

Uploading an Image

To upload a new image (e.g., noble-server-cloudimg-amd64.raw):

  1. Click create Image (top right).
  2. Image Details:

    • Image Name: Enter a descriptive name.
    • File: Select Browse to upload your file.
    • Format: Select RAW disk format and Bare container format.

    Upload Image

    Optimal Formats

    For best performance and compatibility, we recommend using RAW disk format and Bare container format.

Managing Key Pairs

  • Key Pairs: specific SSH keys for accessing instances. Key Pairs List

Networking (Neutron)

Network Visualization

The Network Topology view provides a graphical representation of your infrastructure. Network Topology

Creating a Private Network

  1. Go to NetworkNetworks. Networks List
  2. Click Create Network.
  3. Define the Network Name and Subnet (CIDR, Gateway).
  4. Configure DHCP to automatically assign IP addresses to instances.

Configuring Security Groups

Security groups act as a virtual firewall for your instances. By default, all incoming traffic is blocked. 1. Go to NetworkSecurity Groups. Security Groups List 2. Click Manage Rules on a security group. Security Group Rules 3. Add Rule: Allow specific traffic. * SSH: TCP Port 22 * HTTP/HTTPS: TCP Port 80/443 * ICMP: For ping/traceroute Add Rule Dialog


Load Balancing (Octavia)

To distribute traffic among multiple web servers:

  1. Navigate to NetworkLoad Balancers. Load Balancers List
  2. Click Create Load Balancer.
  3. Load Balancer Details: Name, IP address (VIP), and Subnet.
  4. Listener: Protocol (HTTP/TCP) and Port (e.g., 80).
  5. Pool: The group of backend servers.
  6. Members: Add your actual Compute instances to the pool.
    • Monitor provisioning status until it is Active.

Kubernetes Clusters (Magnum)

Tier5 allows you to deploy fully managed Kubernetes clusters using Magnum.

Advanced Workloads: Kata Containers

For workloads requiring stronger isolation, you can use Kata Containers with your Magnum clusters. See the Kata Containers Guide.

  1. Cluster Templates: Start by selecting or creating a template that defines the OS, Container Runtime (Docker/containerd), and Network Driver. Cluster Templates

  2. Create Cluster: Go to Container InfraClusters and click Create Cluster. Cluster List

  3. Configure Cluster Details: Create Cluster Wizard

    • Master Count: Number of control plane nodes (odd number for HA).
    • Node Count: Number of worker nodes for your applications.
    • Keypair: SSH key for node access. Keypair Selection
  4. Network & Labels:

    • Select the network driver (e.g., Calico, Flannel).
    • Enable Auto-healing or Auto-scaling if required. Autohealing Options
  5. Wait for Creation: The cluster status will move to CREATE_COMPLETE. Cluster Details

Cluster Access

Once the cluster is created, the configuration file (kubeconfig) can be downloaded directly from the API or Dashboard.


Storage (Cinder)

Managing Volumes

Block storage volumes provide persistent storage for instances. Volumes List

  1. Create Volume: Create Volume Dialog
    • Type: Select volume performance tier (e.g., HDD, SSD, NVMe).
    • Size: Capacity in GB.
  2. Attach to Instance:
    • Once created, use Manage Attachments to connect the volume to a running instance.

Volume Snapshots

Snapshots allow you to save the state of a volume at a specific point in time. Volume Snapshots

Volume Backups

Backups allow you to store volume data off-site or on minimal cost storage.

NFS Backups Only

Currently, Tier5 supports only NFS backups which must be configured as an extra service. Please contact the Tier5 support team to enable this feature for your tenant.

Volume Backups


Orchestration (Heat)

Heat allows you to deploy complex infrastructure defined in templates (Infrastructure as Code).

Stacks

A "Stack" is a running instance of a template. Stacks List

  1. Launch Stack:
    • Upload a HOT (Heat Orchestration Template) or AWS CloudFormation template. Template View
  2. Monitor Events:
    • Watch the deployment log to ensure all resources (networks, instances, LBs) are created successfully. Stack Events
  3. Topology:
    • Visualize the resources in your stack. Stack Resources

External Resources