Fuga's dashboard called 'Horizon' is a web-based user interface to OpenStack services. Horizon has grown from a set of views, templates and API calls to a complete support tool for OpenStack projects.
Horizon enables you to manage all your projects within OpenStack. The dashboard gives you easy access to your instances, volumes and lets you easily configure your networks and routers. This tutorial gives you an overview of the basic functionality.
Log on to the dashboard
Not every browser is supported by the OpenStack dashboard. The browser needs support for HTML5 Canvas and HTML5 WebSockets (check compatibility here). Chrome or Firefox are suggested for the best performance.
- For the Fuga dashboard, the URL is as follows:
- Enter your credentials at the logon page and click sign in.
After you log in, the Project tab will appear.
When you click on your project as a user, it shows you some other tabs: From these tabs you can manage your instances, volumes, network etc. The dashboard project tab looks like this:
From the compute tabs you can do the following:
In the overview tab you can find your reports like uptime, the amount of RAM for an instance and how many instances you are using within your project.
From this tab you can connect to your instances through virtual network computing (VNC). The instance tab shows you the instance's name, its private and public IP addresses, size, status, task, power state and uptime. In the action tab you are able to create a snapshot and edit, resize, pause, reboot and much more.
In the volume tab you can create, view and delete volumes. Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach or detach a volume at any time. You are also able to create a snapshot from a volume.
Launch instances from images and snapshots, view images and instance snapshots created by users. There are publicly images available that you can use to create your own images. After clicking on an image you can find some details like size, status, format etc.
Access & Security
Before launching an instance, you should add security group rules to let users connect by ssh and ping to their instance.
- Security Groups: View, create, edit, and delete security groups and security group rules.
- Key Pairs: Each project should have at least one ssh key pair, here you can view, create, edit, import and delete your key pairs.
- Floating IPs: Unlike the state of the instances, floating IP addresses are able to have their connections modified at any time. You can allocate an IP address to a project in this tab.
- API Access: View API endpoints
From the Network tabs you can do the following:
The network topology allows you to see a visual representation of your OpenStack network.
In the network tab you are able to create and manage your public and private networks.
Here you can create routers, give them the name you want and manage your subnets.
Go to the next tutorial in Getting started
Configure secure access for instances (2/5)
Before launching an instance you need to configure a security group. A security group is a set of IP filter rules that defines networking access and makes it possible to grant SSH access to users or be able to ping an instance. By modifying the default group or creating a new one you can attach a security group to (specific) instance(s). Key pairs are SSH credentials that are deployed into an instance when it's first deployed.