• Introduction
• Access and User Profile
• Log in
• User Profile
  • Preferences
  • Support
  • RC File
  • Log out
• About
• Project
• Servers
• Flavors
• Images
• Volumes
• Kubernetes
• Invoice

Introduction

To get started with using your cloud, we introduce ARCUS, OpenStack's dashboard. It is accessible through a web browser and allows a user to interact with the cloud. As an administrator, most of the cloud can be managed this way.

Access and User Profile

Log in

Enter username and password into the login form. If Active Directory domains are in-use, optionally also change the authentication domain.

User Profile

The user profile is located at the top right corner of your browser window.

Click on the username to open a window where you can see preferences, support, and a log out button.

Preferences

Preferences is the first menu option.

The preferences will have a popup window with three different tabs, permitting the following:

• Set Default Language on the current browser
• Create/Upload a public SSH key to be injected into new Linux VMs
• Change the current login password (local users only – no Active Directory support)

Support

Support is the second menu option in the top-right user menu. It redirects the browser window to Breqwatr’s support portal, where users can submit tickets and request help.

Contact Breqwatr Support for enrollment in the support portal.

RC File

RC File is the third menu option in the top-right user menu. It downloads the file that containes the environment variables that are necessary to run OpenStack command-line clients. The file contains tenant-specific environment variables.

Log out

Log out is the bottom option in the top-right user menu.

On a shared workstation, always remember log out correctly using the logout button. Do not simply close the window. Authenticated users’ sessions do eventually expire but remain active for some time.

About

The version identifier shown above the Copyright text is the Breqwatr Web UI’s version. It does not correspond to the installed OpenStack release.

Clicking on the OpenStack button will display a collection of links to API reference pages for the underlying OpenStack projects that make up the Breqwatr private cloud. DevOps professionals can leverage these APIs to automate their infrastructure directly. These same APIs are also commonly abstracted by projects such as Ansible and Terraform.

Project

Servers

Servers list all the VMs created in a given project, along with the controls and information required to create and manage those workloads.

• Quota: displays the available and used quota for resources:
• Instances: Number of VMs created in this project
  • vCPU: Virtual CPU cores
  • vRAM: gigabytes of virtual RAM
  • vDisk: gigabytes of virtual block device storage
• Search: The blue text input at the top allows you to filter servers by name, description, flavor and image names
• Create VM Button: allows you to create VMs using a simplified questionnaire/wizard.
• Pagination: this option will visible only after one VM is created. Limits auto-refreshing display of VM cards to a user-defined size.
• Server Actions: When multiple VMs are selected using the checkbox on the card, Server Actions become available for bulk operations.
• Server Details: When a server card is clicked, a Server Details window will display more information and controls for that VM.
• Server Dropdown: When the “hamburger” context menu is clicked on a server card, common server controls are displayed.

Flavors

Flavors define the size (CPU and RAM) of a given virtual machine. The project flavor page allows a quick at-a-glance view of which flavors are available in a given project. Each project can use all publicly available flavors, along with any flavors that a cloud administrator has marked private and assigned to their project.

When many flavors exist, the search box also allows filtering.

Images

The project image page lists each image available in the selected project. All public images are visible along with any user-created images, which are private to this project. Cloud administrators can also mark images private to specific projects. Non-administrative users may not delete public images, though they may delete their own uploaded ones.

When many images are present, the search bar can be used to filter them.

Volumes

About volumes: - Volumes are the block devices used as disks within virtual machines. - Volumes are only accessible within the project where they exist. - When a volume is not attached to a VM, it still exists as a block device on the storage. - With the exception of boot-volumes, volumes can be removed from servers and attached to other servers. - A volume in the “available” state is not attached to any server right now - A volume in the “in-use” state is currently attached to a server - A volume with “bootable” enabled can be selected in the new VM wizard’s “volume” category. This indicates that the volume is bootable. Trying to boot from a “data volume” – one without the ability to boot an OS, will lead to a server that starts but says it has no boot drive. When there are no volumes in the project, the Volumes page will show a simple create button instead of the data table.

Kubernetes

OpenStack has made the integration consistent and predictable thanks to the APIs that are used by Kubernetes to consume these resources seamlessly. OpenStack, itself, is an abstraction layer that allows consuming compute, storage and networking resources in a consistent manner to its consumers, Kubernetes being one.

Invoice

This page helps users to identify their current and historic expenses. This is a report of a project’s expenditures. Once per month an invoice is automatically generated for the previous month. Invoices present resource-hours multiplied by prices as defined by cloud administrators. Once an invoice exists, any future changes to prices or discounts are not applied backwards in time – generated invoices never change.

Resources are calculated by time-allocated, not “actual use”. For instance, a VM with 8 cores that ran at 10% utilization for a month would still be billed for 8 cores over a month.

Sections:

Month Selection: You can select any month from any year after your account has been created. Download/Print Invoice: Allow the user to print a nice print-friendly representation of the data. To save the data as a PDF, use the web browsers “Print to PDF” functionality.

Invoice Details Summary: Raw resource-hour utilization stats for this project are displayed here Servers: CPU-hours, RAM-hours, base and image prices are reflected here