The Helion Stackato web interface is called the Management Console. The interface displays more options and settings for administrators than it does for regular end users. Some of the features described below are only available in the Admin view.
The Helion Stackato Management Console is a web interface that allows the administration and management of the Helion Stackato Server.
Your hypervisor provides tty console access to each of its virtual machines. After startup, a Helion Stackato VM displays:
Helion Stackato Management Console at
https://stackato-xxxx.local
On a micro cloud VM where the local network
supports multicast DNS, the hostname will be
stackato-xxxx.local. If you have configured the hostname and DNS of the
Helion Stackato server manually, or are connecting to a server administered by
someone else, supply the assigned hostname instead
(for example, api.stackato-test.example.com).
Enter the URL into your web browser, and the Management Console will load. The Console is supported on the following browsers:
Using a browser which fully supports WebSockets is recommended.
Note
The SSL certificate for the Helion Stackato Management Console is self-signed. You will need to manually accept this certificate in your browser. See the HTTPS section for information on using your own certificate.
When you first access the Management Console, you will be prompted to create a primary administrator for Helion Stackato. Enter an email address as the username, set a secure password, then review and accept the license agreement.
Note
The password you choose here becomes the login password for the
stackato user on the VM (for example, for ssh access).
Once you have logged in, you can begin to add other users and admins, enable and disable services, and generally set up the system to your requirements.
Basic Helion Stackato administration can be done through the Management
Console, but some maintenance and configuration tasks may need to be
done at the command line using the kato command. See
Kato Client Command Reference for a full list of options.
Tip
By default, the management console displays a maximum of 50 items per page. To increase or reduce the number of items displayed per page, you can run the following command:
kato config set cloud_controller_ng renderer/default_results_per_page <number>
For more information, see the usage details for the kato config set command.
The top-level page of the Management Console displays quick links to the most used resources and views. The blue buttons are for features also available for regular end users (see Management Console (User View)).
Green buttons expose Admin-only functionality:
Available patches for the system, new Helion Stackato releases, and the latest Helion Stackato news are also displayed on this page.
The Applications section displays a list of all apps on the server. Click anywhere on the line for an app to view its details. Admins have the same permissions in the Application View as a Developer of the space it was deployed to.
The top level Organizations page allows Admins to add and delete organizations. Clicking on an organization name opens its details. This view is the same as a regular user's Organizations view, but administrators can edit quotas, and add/remove domains, spaces, and users.
The Support menu includes the same options as the regular user.
Several views that are only available to Helion Stackato administrators are in the Admin menu.
Displays a list of roles and their status in the system. Additionally, the following system information is displayed:
Displays a list of nodes in the current cluster, and what services are running on each node. In a micro cloud configuration, only the current local node ('127.0.0.1') is displayed.
To enable or disable services on a node, click Configure Roles (cog icon) to see the Node Settings, showing a list of all available roles and checkboxes to enable or disable each one. Click Save to apply changes.
See also the kato role and kato info command documentation for the CLI equivalents, and the Cluster Setup section for information on adding nodes to the cluster.
Displays a list of available patches for the current cluster.
Links to the Applications and organizations lists.
A filterable list of all domains configured on the system, showing whether they are Shared or Owned domains.
A filterable list of routes in the system.
A filterable list of managed service instances on the system.
A filterable list of user provided service instances on the system.
A list of available service types (with their version).
The Users section displays a list of users and admins.
Lists the Quota Plans available to apply to organizations on the system. To edit a definition, click Edit on the right. The following fields can be modified:
sudo privileges
within their application containers.To create a new definition use the stackato quota create command.
Helion Stackato tracks the amount of memory used by applications across all DEA nodes and shows various reports. Available memory is calculated based on the system memory of the DEA nodes multiplied by the Max Memory Percentage. Memory Summary shows how much memory:
Memory usage statistics and a usage bar graph for each DEA node in the pool.
Memory usage statistics and a usage bar graph for all configured Placement Zones
Memory usage statistics and a usage bar graph for all configured Availability Zones
Shows realtime results for incoming requests (connections per second), routing errors (errors per second), and an overview of the cumulative requests to the system.
Displays graphs for server statistics: CPU, Load, Memory, Disk Operations, Disk Space, Processes, and Swap (primary node or micro cloud only).
The Cloud Events section displays a list of events (including errors and warnings) on the Helion Stackato server. The events can be filtered by Severity, Node ID, or Type, or by using a substring match in the Search field.
The Settings menu gives access to the following Console and system settings:
System Settings:
Sample Application URLs: URIs for Store Definition YAML files which populate the Sample Applications page. The URIs need not be public, but must be accessible from the controller node.
Docker App Settings:
Require sudo: Limit Docker image deployment to organizations with 'sudo' permissions enabled in the Quota Plan.
Allow any docker registry: Let users deploy Docker images from any registry server. Docker image deployment should be limited to either a trusted group of users, trusted image sources, or both. Allowing any user to deploy Docker images without restrictions is not recommended.
Allowed Docker Registries: A list of servers, namespaces, or images that
users are allowed to deploy. Entries are specified in the standard
format accepted by the docker client
(user:pass@domain.com:port/namespace/repo:tag). For example:
| Pattern | What it allows |
|---|---|
| httpd | the 'library/httpd' repo on Docker Hub, any tag |
| httpd: | only 'library/httpd:latest' |
| httpd:2.4 | only 'library/httpd:2.4' |
| cloudfoundry/ | Docker Hub repos under the 'cloudfoundry' namespace, any tag |
| cloudfoundry/lattice-app | only 'cloudfoundry/lattice-app', any tag |
| reg.example.com | any namespace, repo, and tag on private registry |
| reg.example.com/ | any repo in the 'library' namespace |
| reg.example.com/prod | any repo in the 'prod' namespace, any tag |
| reg.example.com/prod/app | only the 'prod/app' repo, any tag |
| reg.example.com/prod/app: | only 'prod/app:latest' |
| reg.example.com/prod/app:mytag | only 'prod/app:mytag' |
| reg.example.com:5000 | a registry server running on a specific port |
| user:pass@reg.example.com | a registry server requiring login |
Credentials specified in the Allowed Docker Registries list are used as defaults when the user requests a matching image name without credentials.
Allowed Repos: Debian package repositories allowed in application
containers. End users can install additional packages (for example, with
apt-get or aptitude) only from these repositories. When adding
new repositories, GPG keys for each new repo must also be added to the
Docker base container (see Allowed Repositories).
api), or for cases where a particular DNS sub-domain
record is not being resolved to the Helion Stackato system. Specify only the
host (subdomain) portion of the URI. Fully qualified URLs will be
ignored.Various settings and templates to customize the look and feel of the Management Console. The settings are divided into the following categories:
en and de
are available), or choose a different URL for documentation.Detailed instructions for customizing and branding Helion Stackato can be found in the Theming and Customization section.
A filterable list of DEA Placement Zones on the system.
A filterable list of Availability Zones on the system.
Specific permissions allowing organization managers and developers to perform certain tasks can be toggled by admins using feature flags. When disabled, only admins can perform these tasks.
These options can also be toggled using the stackato CLI client with
the feature flags commands.
Lists current log Drains and the log drain retry limits. Drains and limits cannot be changed in this interface; use the kato log drain ... commands and kato config ... commands.
Settings for the Harbor TCP/UDP port service.
See Harbor: Requirements & Setup for more information.
You may use the VirtualBox distribution of HPE Helion Stackato as a stand-alone micro cloud system with up to 4GB of RAM under the Product Evaluation Agreement.
All other distributions of HPE Helion Stackato are subject to the Software License Terms and require a software license key.
For Helion Stackato pricing and options, contact stackato-sales@hpe.com.
