embl-ebi-tsi / ebi-cloud-portal-app

An Angular 2 web application for the EBI Cloud Portal API

Note The EBI Cloud Portal has been retired and its code base is no longer updated. If you would like to contact the Cloud Portal authors, please leave us feedback via the EBI contact form mentioning the EBI Cloud Portal in the Subject.

EBI Cloud Portal

This project was generated with Angular CLI version 1.0.0.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor. Before running the tests make sure you are serving the app via ng serve.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

ebi-cloud-portal-app's Issues

Applications ordering in the Repository

Applications seem to be listed in a kind-of-random order in the repository.

It would be nice to have them sorted alphabetically or in some other predictable order (possibly chosen from a drop-down list by the user?).

Default input inconsistent behaviour

While deploying an application is allowed to left the input field void.
If the field is void and the application provide a default value for the input the deployment will be successful.

The problem.
If you start write something in the input field and then cancel it (or maybe just selecting the field with the mouse pointer), the above behaviour will change and the void string will be provided as a value for that input, overwriting the default value.

Deployment parameters templates

Suggested by @erikvdbergh :

From an application deployment parameters list, pre-populate the list of fields on the new Deployment Parameters dialog.

'Create deployment parameter' dialog button placement

In the deployment parameter creation and edit dialog, I constantly hit the 'Add' button when I want to add a new parameter, but instead, this closes the dialog. The current placement of the '+' button up top and the 'Add' button right where you are writing is very confusing.

A suggestion would be to have a 'Add parameter' button at the bottom-left (in yellow?), and a 'Done' button (in green) at the bottom right, which would bring a more natural flow to the UX.

Not critical, but it still gets me every time.

Cheers

"login" link does not work from the /welcome page

It's quite a strange one: it seems we're serving the same page from /about and /welcome, yet the "login" link works fine when accessing it from /about and not from /welcome.

To get to the /welcome page: Sign On and Logout. Then try click on the "login" link, in the "Then you can login" paragraph. Notice how nothing happens but you're now on the /welcome/signon page. Every time you click on that "login" link, you'll get an extra /signon.

Per provider deployment parameters, instead of per provider inputs

Something we are running into right now is that deployment parameters are often provider specific, but inputs are not.

At the moment, we can specify per provider inputs, but not per provider deployments parameters, whereas the other way around would be more useful.

IMO, inputs are things that change with each deployment, meaning after you have set up your cloud provider. Deployment parameters are specific to providers, but not to individual deployments. This also follows out of the fact that they are tied in with a cloud provider through a configuration.

This is especially important now that deployment parameters are validated at deployment time, which means I am including a lot of dummy variables for separate providers.

Cheers

GCP provider label not aligning correctly

GCP label on the Application card doesn't align properly, see screenshot.

Double click for opening deployment status page

Would be possible, in the deployments page, to open the deployment info only with a double click instead of a single click?

The use case:
An user try to copy a deployment value, using the mouse, from the global deployments page, but as soon as he releases the mouse button, the interface opens the deployment information page of the specific deployment.

Visualize the name of the `configuration`

When you create a new deployment from the Application repository page, the first indication is:
Select configuration but there is no indication of the name of the configuration.

I understand, most of the time, is more understandable visualizing the cloud provider and the associated deployment parameters, but the actual status is quite confusing.
It would clearer, if the portal showed also the name of the configuration (including the underlying composition).

Alternatively, we can change the way the configurations are displayed, putting less stress on the name of the configuration (that in this moment is completely useless) and stressing more the combination of his components (cloud provider - and deployment parameter), in order to match the behaviour of the portal during the deployment.

Deployment destroy logs are hidden on DESTROY_FAILED

Currently, the app shows the Deployment destroy logs while destroying, but hides them when the status becomes DESTROY_FAILED.

It would be better to keep them there to help the user understanding what's the issue.

"Sign on" not clickable on mobile site

The rendering of the cloud portal using mobile phones is not perfect but still usable. The biggest issue is that is not possible to reach the login page pressing on "sign on".
Tested with chrome on an Android device.

A 'Refresh from repo' button for applications

A button to press from within an application to do a git pull for the repo would be very convenient.

Deployment logs don't display properly

Deployment logs for long deployments don't display properly in the sub-window.

Initially, everything works fine, but after enough logs build up the top of the sub-window becomes blank as below

Scrolling down eventually shows the logs but the sub-window at this point doesn't tail the logs anymore and the user is forced to keep scrolling manually.

Cloud credentials templates

When creating Cloud Credentials, it would be great if there could be a templated set of variables that appear when you select the Cloud Provider.

I can provide lists of the variables needed, will update this Issue with them ASAP