rasmus/blades-ssh-scraper
rasmus
/
blades-ssh-scraper
1
0
Fork 0
Code Issues 6 Pull Requests Activity

Concurrent direct blade connections. #7

New Issue
Open
opened 2020-12-23 18:49:33 +00:00 by rasmus · 0 comments
rasmus commented 2020-12-23 18:49:33 +00:00
Owner
Copy Link

Kind of Ansibleification of this very very bad interface. Maybe it's a bit overkill? :D

Depends on #6
Helps with #1

  1. On first run, throw ssh key to all blade's ilo, enable ssh, etc. Get hostnames/endpoints to connect to for blades.
  2. On all next runs, connect to enc, get list of blades (if something has changed, been added, removed, etc).
  3. Attempt to async connect to each blade individually. (This could be happening while the enc is being accessed.)
  4. If failure to auth, go through the enc, and copy ssh key once again. Don't end there though. Use the already alive connection.

The point of this is to send a command to all blade's iLOs at the same time. Whatever, go read ansible docs instead.

It may be possible to hack/homebrew the OA, to bypass/fake the SSH connection limit, and just go to the enc over 16 connections, and connect server n from there. Maybe even get it reporting on it's own. Root shell would be nice xD

Kind of Ansibleification of this very very bad interface. Maybe it's a bit overkill? :D Depends on #6 Helps with #1 1. On first run, throw ssh key to all blade's ilo, enable ssh, etc. Get hostnames/endpoints to connect to for blades. 1. On all next runs, connect to enc, get list of blades (if something has changed, been added, removed, etc). 1. Attempt to async connect to each blade individually. (This could be happening while the enc is being accessed.) 1. If failure to auth, go through the enc, and copy ssh key once again. Don't end there though. Use the already alive connection. The point of this is to send a command to all blade's iLOs at the same time. Whatever, go read ansible docs instead. It may be possible to hack/homebrew the OA, to bypass/fake the SSH connection limit, and just go to the enc over 16 connections, and connect server n from there. Maybe even get it reporting on it's own. Root shell would be nice xD
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: rasmus/blades-ssh-scraper#7
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?