azimuth-cloud / azimuth Goto Github PK

License: Other

Dockerfile 0.48% Python 50.53% HTML 1.12% Smarty 0.23% CSS 1.34% JavaScript 46.25% Shell 0.06%

azimuth's Issues

UI: server active tasks means table is too wide

when you reboot servers, the table width seems all wrong, and on chrome you don't get scroll bars or any obvious clues, just get buttons hiding on the right hand side.

Maybe we need to fix the width of something better here?

Enable per appliance filtering or other specification of applicable flavours

It would be most useful to have the capability of filtering the list of flavours, or otherwise specifying a list of applicable flavours, per appliance type. A trivial examples:

Present only "Intel" flavours in the dropdown for appliances dedicated to Intel workloads
Present only flavours with RAM > 128 GB for appliances requiring large allocations

Error boundary for unknown errors

Update slurm with changed number of compute nodes doesn't deploy additional node

Create a cluster with 1x compute node
Press Update and add another compute node.
No additional node was created. The stackhpc.terraform.infra : Provision infrastructure using Terraform step was an "OK" (not changed).
From K8s:

$ kubectl -n az-rcp-cloud-portal-demo describe clusters.caas.azimuth.stackhpc.com slurm-v1

Status:
  Applied Extra Vars:
  ...
    compute_count:                      1
    ...

so looks like this didn't get updated.

This did used to work.

Terraform platform modals could show component machines

Encrypt Django session cookies

Azimuth can present FIPs for selection which aren't actually available

Selected an IP on Arcus when creating a platform with a FIP, creation failedwith a popup:
{"parameter_values":{"cluster_floating_ip":"External IP is not available."}}

Horizon showed the FIP as Active but not mapped to a fixed IP. However the CLI showed it was mapped to a port on the ilab-60 network which was not owned by the project being used.

Allow the "landing page" to be customised

Redirect from login to Quotas or Platforms (or somewhere else)

Some errors make the screen go blank, need to be more defensive?

For example, if you use the CRD driver, you can delete a cluster type, but still have a cluster of that type, and the whole screen goes blank. There are some react error messages suggesting we are missing some error handlers to pop up a more friendly error message, so we fail more gracefully. These are mostly unexpected cases, like the choices param not being well formed in ui meta causing the screen to go blank.

Feature: event handler for irreconcilable (k8s) clusters

Description

There are situations where a kubernetes cluster administrator may use the UI to
create / update a cluster that is beyond the scope of the underlying cloud
infrastructure. Such a request may be considered "irreconcilable". Like certain
types of romantic poetry, it is full of subtle longing for things that will
likely never come to pass.
One such situation is where the user submits a request to update the cluster,
and in doing so specifies a set of resources that exceed the given quota for the
tenancy where the cluster is deployed. After such a request has been issued, the
update button for that cluster becomes unusable and the only ways to get back to
a good state is to resolve the issue on the openstack side, delete the
cluster, or intervene using the azimuth cli.
Note that the k8s cluster under management and the applications it runs remain
functional during this blip.

Desired behaviour

The user has the option to roll back to a previously valid cluster configuration after a timeout.
For instance, after the timeout has been exceeded, the user would be presented with a modal
that gives a choice of either to continue to wait or to revert the cluster to the last known good state.

One possible Implementation suggestion

Add a representation for "previously good k8s cluster form state" to the store
Also add a state to represent "irreconcilable k8s cluster"
Modify KubernetesClusterModalForm and useKubernetesClusterFormState to
use a "copy-on-write" style pattern to store the result of
initialState(kubernetesCluster) before attempting the update.
In the case that we enter the "irreconcilable k8s cluster", allow the user to
re-apply the stored "previously good k8s cluster form state"

Nunjucks templated values don't update in UI

Appliance properties displayed in the UI via nunjucks templates don't update when the appliance is updated. For example, we allow the user to update the number of IPUs their machine has available. If the user changes the number, and updates the appliance, the new IPU count isn't displayed in the UI (the IPU count is also populated into the instance metadata, and is correctly updated there).

There appears to be nothing the user can do to force an update: refreshing the details pane doesn't help; refreshing the main dashboard page doesn't help; logging out and back in doesn't help.

Advance create platform dialog as soon as platform has been selected

We've had a question from our Azimuth users whether, when an appliance has been selected in the "Create a new platform / Pick a platform type" dialog, can it automatically progress to the "Configure platform" page? This would be rather than the current workflow that requires clicking the "Next" button. Thanks