-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
adds tcp_ping plugin #13
adds tcp_ping plugin #13
Conversation
Very nice! |
Test seems to be failing though, looks like localhost:22 is open while you expected it to be closed (inventory sets the ip of the fake devices to localhost) |
Interesting.
Ideally we would be able to reproduce this test "locally"
as well. Which is not the case right now, the container and my machine don't
listen on 22/tcp.
I can setup openssh (or something else) to have a local listening socket
in the container easily.
But it raises another question, I'm also looking into porting over the
command and remote_command tasks. For the testing of the remote_command task we would
need to have an openssh server.
Not sure if it is possible to do that with github runners. Not sure if
we can properly authenticate to the openssh server running on the
runner. (I'm not aware of the username/password and I seem to be unable
to create a ~/.ssh/authorized_keys file).
The only option I see is to run all of the tests in a container on the
runner, and spin up additional containers for each host defined in the
"inventory" (potentiall using your stupid_ssh_server).
But maybe I'm missing something here...
|
Github actions supports docker-compose so we could potentially start a few linux containers with openssh and use them for testing. We used to do that actually: |
Yep. I'll take a shot at it.
David Barroso ***@***.***> writes:
… Github actions supports docker-compose so we could potentially start a few linux containers with openssh and use them for testing. We used to do that actually:
nornir-automation/nornir@45c30a7
|
e82a951
to
3c2eb67
Compare
- adds start_dev_env and stop_dev_env makefile targets - adds docker-compose file - modifies jupyter makefile target to run on host instead of docker container - add docker-jupyter makefile target to run jupyter notebook server in docker container
b8185f9
to
8d64225
Compare
43a75ab
to
d5ed058
Compare
This one should be good now. There's a few changes:
|
A thousand apologies, i have no clue how I missed this PR for so long... Rebasing and merging. Sorry again for missing this :( |
Awesome! No need to apologize :) |
adds tcp_ping plugin
closes nornir-automation/nornir#520