Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Computer configuration #1974

Closed
espenfl opened this issue Sep 18, 2018 · 7 comments
Closed

Computer configuration #1974

espenfl opened this issue Sep 18, 2018 · 7 comments

Comments

@espenfl
Copy link
Contributor

espenfl commented Sep 18, 2018

The walk through for the computer configuration could be improved:

  • Look for keys (what do we answer and what does this really mean?), passing false here still leads to the request of the SSH key file
  • SHH key file (is this loaded, or does Aiida use this...security concerned users would just abort here unless one is a bit more specific)
  • Allow ssh agent (what does this mean and what kind of agent is used?)
  • SSH proxy command (this is fine, maybe mention a default, like disabled if you just press enter?)
@ltalirz
Copy link
Member

ltalirz commented Sep 26, 2018

Assigning @giovannipizzi as he worked on the computer setup migration to click (for configure, it was actually @DropD...).

I actually have a few more questions concerning verdi computer configure:

  1. why is it necessary to pass local/ssh if the computer stores this information anyhow? This makes the cli harder to use
  2. why is it necessary to have a separate verdi computer configure show command? why can't we just show all the necessary information with verdi computer show?

@giovannipizzi
Copy link
Member

Is this partially related to the discussion on #1893?

@giovannipizzi
Copy link
Member

To answer @ltalirz - the reason for the current design is to allow us to implement also the configure commands as plugins (they actually use - as parameters - the content of what is in the transport plugin). We didn't find a proper way to define a single command (e.g. verdi computer configure) that was allowing to define, at module load time (as click wants) and not at runtime which interactive options each of the two configure commands wants (they are different for every transport, we wanted to have both interactive and non-interactive behaviour, and define the options at the click level).
Of course if good ideas are available, happy to discuss/implement them!

Also - the idea is that things in the configure are connection/authorization specific, while in setup are needed just to set up a code that you don't necessarily want to connect to (e.g. the case when you import a code - it's set up, but not configured).

About the original questions, I agree, I think some of these are being tackled in #1893 - @waychal can you take into account also of Espen's comments here?

@sphuber
Copy link
Contributor

sphuber commented Oct 12, 2018

The issue in #1893 concerned actual bugs, not user-friendliness improvement. Those bugs have been addressed in PR #2054 but the questions posed here about the interactive flow remain relevant

@giovannipizzi
Copy link
Member

Some of these points, if still valid, could be addressed in the revamped docs?

@sphuber
Copy link
Contributor

sphuber commented Oct 14, 2020

The main part of this issue, the looking for keys, will be addressed by #4387 . The other points are mostly requests to improve the help string of verdi computer configure. @espenfl is this still relevant, or can this be closed?

@espenfl
Copy link
Contributor Author

espenfl commented Oct 14, 2020

@sphuber Have not checked the remaining points. Please close and then I can reopen on specifics if I detect something on next install.

@sphuber sphuber closed this as completed Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment