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.

Sign up for GitHub

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

Jump to bottom

burn: add ssh/conf in each node with stricthostkeychecking off #30

Open
4 of 7 tasks
dkkolli opened this issue Apr 19, 2022 · 1 comment
Open
4 of 7 tasks

burn: add ssh/conf in each node with stricthostkeychecking off #30

dkkolli opened this issue Apr 19, 2022 · 1 comment
Assignees
@jpfleischer
Labels
1 priority one (highest) question Further information is requested

Comments

@dkkolli
Copy link
Collaborator

dkkolli commented Apr 19, 2022 •
edited by jpfleischer
Loading

  • stricthostkeychecking off on
  • proxyjump off on
  • we need to implement a function that reads it as a lowercase string, and sees if it is y, true, t, etc.
  • test if it works (JP)
  • test if it works Gregor
  • test if it works DK
  • new release of cloudmesh.common

comment from JP: this is meant to add ssh/conf on each raspberry pi node, manager and workers? if so, then cms host key access does this, but it does NOT have proxyjump. is proxyjump necessary? should we add proxyjump to access command? i think we are confusing ssh/conf on each node, with the cms host config.

cms host config relates to the host, or the laptop/desktop used to ssh into pis
@laszewsk laszewsk changed the title add ssh/conf in each node with stricthostkeychecking off burn: add ssh/conf in each node with stricthostkeychecking off May 2, 2022
@laszewsk laszewsk added the burn label May 2, 2022
@jpfleischer
Copy link
Member

https://cloudmesh.github.io/pi/tutorial/raspberry-burn-windows/#74-activate-no-stricthostkeychecking

@jpfleischer jpfleischer transferred this issue from cloudmesh/cloudmesh-pi-cluster May 2, 2022
@jpfleischer jpfleischer added the 1 priority one (highest) label May 2, 2022
This was referenced May 2, 2022
Closed
Open
Closed
@jpfleischer jpfleischer added question Further information is requested and removed burn labels May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpfleischer jpfleischer

Labels
1 priority one (highest) question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@laszewsk @dkkolli @jpfleischer