A Web UI for interacting with Airship-managed clusters
Go to file
Schiefelbein, Andrew d1a0509bf0 Fixed the ctl + c exit
The removal of electron was a bit too expeditious and removed
some of the things that controled the exit of the system

Change-Id: I8ad1ab83fc3ecbcbe07bdd949bc01fd8a0889e00
2020-07-31 08:48:13 -05:00
.github Update Airship vulnerability link 2020-05-18 21:22:07 +00:00
certs update makefile to build docker images 2020-07-08 08:45:00 -05:00
cmd/airshipui Fix for minor Go lint issues 2020-06-17 16:38:52 -05:00
docs Remove electron from the tree 2020-07-29 09:48:49 -05:00
examples Fix for minor Go lint issues 2020-06-17 16:38:52 -05:00
internal Fixed the ctl + c exit 2020-07-31 08:48:13 -05:00
playbooks Added unit-tests in Makefile 2020-07-22 14:06:02 -04:00
roles/docker-install Update zuul gates to use docker-image 2020-07-09 13:12:10 -05:00
testutil SSO ability for plugin dashboards 2020-07-28 13:24:06 -05:00
tools Incorporate the whitespace linter from the CTL project 2020-07-22 13:40:32 -05:00
web Remove electron from the tree 2020-07-29 09:48:49 -05:00
.gitignore Incorporate the whitespace linter from the CTL project 2020-07-22 13:40:32 -05:00
.gitreview Add a .gitreview 2019-12-06 16:02:18 -06:00
.golangci.yaml [linters] Aligning linter config with airshipctl 2020-06-19 11:38:46 -05:00
.zuul.yaml Update zuul gates to use docker-image 2020-07-09 13:12:10 -05:00
Dockerfile update makefile to build docker images 2020-07-08 08:45:00 -05:00
go.mod Add gomod tidy check to lint gate 2020-07-13 14:24:18 -05:00
go.sum SSO ability for plugin dashboards 2020-07-28 13:24:06 -05:00
LICENSE Incorporate the whitespace linter from the CTL project 2020-07-22 13:40:32 -05:00
Makefile Merge "Incorporate the whitespace linter from the CTL project" 2020-07-24 14:36:35 +00:00
README.md Remove electron from the tree 2020-07-29 09:48:49 -05:00
tox.ini Publish documentation 2020-05-11 21:21:41 +00:00

Airship UI

Airship UI is a browser based application that is designed to allow you to interact with Airship components, find and connect to the kubernetes cluster and use plugins to tie together a singular dashboard to view addons without the need to go to a separate url or application.

Prerequisites

Getting Started

git clone https://opendev.org/airship/airshipui
cd airshipui
make
make install-npm-modules # Note running behind a proxy can cause issues, notes on solving is in the Appendix of the Developer's Guide

Adding Additional Functionality

Airship UI can be seamlessly integrated with service dashboards and other web-based tools by providing the necessary configuration in $HOME/.airship/airshipui.json.

To add service dashboards, create a section at the top level of airshipui.json as follows:

"dashboards": [
        {
            "name": "ceph",
            "name": "Ceph",
            "baseURL": "https://ceph-dash.example.domain",
            "path": ""
        },
        {
            "name": "Horizon",
            "baseURL": "http://horizon",
            "path": "dashboard/auth/login"
        }
]

For dashboards that are made available through service endpoints in your cluster, the FQDN for the dashboard will be constructed using the format "hostname.namespace.baseFqdn". In the above example, the configuration for Horizon specifies a service dashboard available at "http://horizon.openstack.svc.cluster.local:80/dashboard/auth/login"

Alternatively, you may choose to specify the FQDN directly, as in the above Ceph example. This configuration specifies a Ceph dashboard available at "https://ceph-dash.example.domain:443/"

If both "hostname" and "fqdn" are provided, "fqdn" will take precedence.

The airshipui.json configuration file can also be used to launch external executables that server your dashboards, in the background as Airship UI starts. Any processes launched by Airship UI will be terminated when Airship UI exits, including any child processes started by the plugins. If the plugin launches a web dashboard, it can be also be included in the list of service dashboards within Airship UI. The following example demonstrates how to add configuration to launch and use Octant within Airship UI:

"dashboards": [
        {
            "name": "Octant",
            "baseURL": "http://localhost:7777",
            "path": "",
            "executable": {
                "autoStart": true,
                "filepath": "/usr/local/bin/octant",
                "args": [
                    "--disable-open-browser",
                    "--kubeconfig",
                    "/home/ubuntu/.airship/kubeconfig"
                ]
            }
        }
]

To prevent a dashboard executable from launching but retain its configuration for later use, simply set "autoStart" to false.

Developer's Guide

Instructions on setting up a development environment and more details can be found in the Developer's Guide