Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@sabinem
Copy link
Contributor

@sabinem sabinem commented May 15, 2024

Relase 0.3.0:

Status of bug fixes and comments:

  • 1. Home page: aligned elements and tried to improve on the content
  • 2. Menu Bar: removed "run" from the navigation: then it makes no longer sense to select the execution on the run page. Therefore it is now selected on the execution page and the user accesses the run page with an already selected execution. This also makes the run page easier to understand.
  • 3. User: The user is now able to add a new directory as work directory on the user page
  • 4. General Layout: the general layout is now changed and the workarea has been integrated into the page
  • 5. Components: the component page has now the select tab renamed to component options where a component can be selected and versions can be added
  • 6. Manage Executions > Select and Execution: the button to unselect an execution has been renamed as suggested
  • 7. Manage Executions > Select Execution: new line on the parameter form and ports fields have been renamed as suggested. A check mark has been added to indicated that a parameter file was uploaded
  • 8. Manage Executions > Sidebar (Work Area): the workarea information has been added for the execution
  • 9 Prepare and Run Executions: Enter secrets manually: this was postponed to the next release, see comment below and the other button I don't want to rename it since it does not open the logging but really just show the output folder.
  • 10. Prepare and Run Executions: The behavoiur of the run button is correct, it just sometimes takes a lot of time until something happens.

sabinem and others added 7 commits May 15, 2024 10:22
pymongo upgrade is needed for security
both code files are currently not used and are therefore removed
from the code base
make execution forms user friendly

for the execution create form it is now possible to add form
fields in a more flexible way on demand rather then knowing
in advance how much steps, parameters and ports should be
added

it can be configured to add a JSON Editor for showing the
progress in the execution create and run form

for execution runs a better workflow is provided: all that belongs
to the run of an execution is now stored in one run object that
can also be viewed in a json editor if configured.
refactor(dashboard execution pages): execution form user friendly
chore: remove unused code barfi and models
@caviri
Copy link
Member

caviri commented May 16, 2024

Hello @sabinem, I'm building and testing the ODTP GUI on my Windows machine.

I'm going to list here my suggestions and bugs I'm catching:

  1. Home.

image

Check out documentation appears misplaced to the right. I would be more coherent to put if below. Also. I would add a little and concise list of the steps that are needed based on the most common cases. But this last is not urgent.

  1. Menu bar.

A run is one action related to execution, so it would be better to include it within executions. If we want a shortcut, we can add a link to the section within Executions.

  1. Users

image

How feasible is adding a button to create a new folder when setting the working directory?

  1. General Layout.

The sidebar with the working area and other information is on the right, which feels a bit strange. Did you test the feeling of placing this to the right?

Also, this sidebar disappears when the screen width is minimized.

  1. Components.

In the tabs menu, Add version at the same level of Add component. Add version should be a submenu under component selection. I would rename Select Component to Component options or Component settings and add the option to add a new version in that tab.

  1. Manage Executions > Select and Execution

Change Cancel execution selection to Unselect execution.

  1. Manage Executions > Select Execution

Amazing way of adding steps to the workflow. Great work @sabinem!!

Regarding the parameters from files, is there any way to change the icon or the color once you pick the parameters?

Parameters overwriting: Change Add/Remove line by Add/Remove parameter.

Ports. Change Ports to Ports mapping (XXXX:XXXX)

  1. Manage Executions > Sidebar (Work Area)

Missing work directory information.

  1. Prepare and Run Executions

Add the possibility to add secret fields. This is fine if the users needs it. However, make them "star" coded? Like ***********

I'm currently running the whole corsica pipeline. But Amazing work Sabine!

@caviri
Copy link
Member

caviri commented May 16, 2024

  1. Prepare and Run Executions
  • Change Check output in project folder to Open Logging.
  • When I clicked on Run execution the modal shows ....loading
    image

@sabinem
Copy link
Contributor Author

sabinem commented May 27, 2024

@caviri I want to discuss with you on

  1. Prepare and Run Executions
    Add the possibility to add secret fields. This is fine if the users needs it. However, make them "star" coded? Like ***********

I would like to postpone this, unless you help me solve the problem I have with this:

  • for the parameters there is no problem to overwrite them, as they are stored as variables in the mongodb and taken from there in CLI command odtp execution run --project-path /Users/smaennel/odtp/digital-twins/testagain --execution-id 665447b2d8e14289615ef5a7 --secrets-files file.txt

But the secrets are taken from file. And the GUI starts the CLI command. Otherwise I would have to call the WorkflowManager directly, but it a long running process and should rather run in the background, therefore I went with starting the CLI command.

To be able to overwrite secrets, the CLI command would have to be changed, so that is not only takes files but also variables.

I would suggest to leave it as it is for now, since it is possible to provide secrets, you just have to add them via files.
What do you think or suggest? It would be for sure a lot of work if we want to implement the feature that you suggest here.

sabinem added 19 commits May 27, 2024 13:15
it should be accessible via the execution page
align in  a reliable way with markdown

add more links on the homepage
integrate it into the page, so that it does not disappear when the
page width is reduced

leave out unnecessary information
add functionality that user can create a new directory as working
directory
automatically select a user when it has been added
adding versiob is now part of options for components

the workarea is integretd into the page
since the function is now only used here
use a common layout for all dashboard pages
automatically select a digital twin when it has been added
when parameters files are uploaded for components, then add a
check mark, so that the users know that this has been done
succcessfully
@sabinem
Copy link
Contributor Author

sabinem commented Jun 18, 2024

@caviri Can you please take another look at the PR and approve if possible. I have followed up on your suggestions and also added the following features:

  • dev set up of docker compose, where the project is installed editable
  • indicators on the dashboard to show the connections to S3, Mongodb and Git
  • additional log level for the run of components, so that the log level there can be higher than the log level on the dashboard
  • improved logging during the run of executions: have custom loggers and use log.exception rather then log.error

@caviri
Copy link
Member

caviri commented Jun 18, 2024

Hello @sabinem, thank you! Can we have a two docker compose? One for dev and the other for "production"? It can happen that some users might change the branch on local potentially affecting to the files located on the docker, so I think it's better to reduce the amount of volumes mounted. What do you think?

sabinem and others added 2 commits June 18, 2024 22:20
Make code base editable in docker compose depending on a variable in the `.env` file

* feat: Add pip install args
* fix(compose.yml): mount docker service

---------

Co-authored-by: Gabriel Nützi <[email protected]>
Co-authored-by: sabinem <[email protected]>
@sabinem
Copy link
Contributor Author

sabinem commented Jun 19, 2024

@caviri We added a setting that decides whether the code base will be editable. Hope this is considered by you good enough to take care of your concern on not having the code base editable in production.

@caviri
Copy link
Member

caviri commented Jun 19, 2024

Good morning @sabinem, not fully convinced. What would be the point of having an /app volume mounted, then? My concern wasn't about the --editable flag, which I think it can remains. But rather with the /app volume mounted which I think it's not necessary on normal conditions of use. The inclusion of the --editable flag solves the problem I described above, however I think that can be simpler. Why not considering a compose for development and another for production?

Also we can take the opportunity to simplify the "production" compose by uploading the image to dockerhub and making not necessary to clone the repo and build the image in order to deploy the platform.

@caviri
Copy link
Member

caviri commented Jun 19, 2024 via email

@sabinem
Copy link
Contributor Author

sabinem commented Jun 19, 2024

@caviri I have spilt the compose.yml into a compose.dev.yml and compose.prod.yml as you suggested. Can you please take another look on the PR now?

@sabinem sabinem merged commit b63ac2e into main Jun 19, 2024
@sabinem sabinem deleted the release0.3.0 branch June 19, 2024 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants