Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 1. HawtIO release notes
This chapter provides release information about HawtIO Diagnostic Console Guide.
1.1. HawtIO features
HawtIO Diagnostic Console is available for general release in the HawtIO Diagnostic Console Guide 4.0.0.
HawtIO includes the following main features:
- Runtime management of JVM via JMX, especially that of Camel applications and AMQ broker, with specialised views
- Visualisation and debugging/tracing of Camel routes
- Simple managing and monitoring of application metrics
1.1.1. Release features
UI plugins
- Connect
- JMX
- Camel
- Runtime
- Logs
- Quartz
- Spring Boot
- UI extension with custom plugins
Authentication
- RBAC
- BASIC Authentication
- Spring Security
- Keycloak
HawtIO Operator
Managing HawtIO Online instances via HawtIO Custom Resources (CR)
- Addition of CR through the OpenShift Console;
-
Addition of CR using CLI tools, eg.
oc; - Deletion of CR through OpenShift Console or CLI results in removal of all owned HawtIO resources, inc. ConfigMaps, Deployments, ReplicationController etc.;
- Removal of operator-managed pod or other resource results in replacement being generated;
- Addition of property or modification of existing property, eg. CPU, Memory or custom configmap, results in new pod being deployed comprising the updated values
Installation via Operator Hub
- Upgrade of operator will take place if the Tech Preview version has been previously installed. The 1.0.0 GA operator will report itself in the catalog as 1.0.1, purely to differentiate itself from the Tech Preview version;
- Successful installs via either the numbered (2.x) or the latest channels will result in the same operator version and operand being installed;
- Successful install of the operator through the catalog;
- Searching for HawtIO in the catalog will return both the product and community versions of the operator. Correct identification of the versions should be obvious.
HawtIO Online
With no credentials supplied, the application should redirect to the OpenShift authentication page
- The entering of correct OpenShift-supplied credentials should redirect back to the Discovery page of the application;
- The entering of incorrect OpenShift-supplied credentials should result in the user being instructed that logging-in cannot be completed;
Discovery
- Only jolokia-enabled pods should be visible either in the same namespace (Namespace mode) or across the cluster (Cluster mode);
- Pods should display the correct status (up or down) through their status icons;
- Only those pods that have a working status should be capable of connection (connect button visible);
- The OpenShift console URL should have been populated by the startup scripts of HawtIO. Therefore, all labels relating to a feature accessible in the OpenShift console should have hyperlinks that open to the respective console target;
- The OpenShift console should be accessible from a link in the dropdown menu in the head bar of the application;
- All jolokia-enabled apps should have links listed in the dropdown menu in the head bar of the application;
Connection to HawtIO-enabled applications
- Clicking the Connect button next to a pod in the Discovery page should open a new window/tab and ‘connect’ to the destination app. This should manifest as the HawtIO Online UI showing plugin names vertically down the left sidebar, eg. JMX, and details of the respective focused plugin displayed in the remainder of the page;
- Failure to connect to a pod should present the user with some kind of error message;
- Once connected, all features listed in the ‘UI Plugins’ (above) should be available for testing where applicable to the target application.
1.1.2. HawtIO known issues
The following issue remain with HawtIO for this release:
HAWNG-147 Fuse web console - support both RH-SSO and Properties login
When Keycloak/RH-SSO is configured for web console authentication, the user is automatically redirected to the Keycloak login page. There is no option for the user to attempt local/properties authentication, even if that JAAS module is also configured.
HAWNG-698 Camel 4 application’s Fuse Console is not loading properly and throwing 'No Selected Container'
Camel 4 application’s Fuse Console is not loading properly and throwing 'No Selected Container'. Errors returned are (502) Bad Gateway and (504) ERR_INSUFIENT_RESOURCE.
