-
Notifications
You must be signed in to change notification settings - Fork 312
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
Provider checker API #6047
Provider checker API #6047
Conversation
782e1ed
to
a464dbf
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #6047 +/- ##
===========================================
- Coverage 37.92% 27.85% -10.08%
===========================================
Files 371 524 +153
Lines 20715 30679 +9964
===========================================
+ Hits 7856 8545 +689
- Misses 12075 21310 +9235
- Partials 784 824 +40 ☔ View full report in Codecov by Sentry. |
ef81c6a
to
cc91377
Compare
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
4478b3c
to
e198aaa
Compare
157e935
to
03c6753
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have a task for this with requirements? From now it looks like it duplicates what we have for providers checks in the monitoring agent.
The difference from monitoring agent is the capability to function w/o using OS-based network interfaces, thus making it more cloud-friendly or suitable for non-Linux (e.g. Windows). One of the real applications of that API is search of provider nodes affected by bug #6022 |
Signed-off-by: Anton Litvinov <[email protected]>
Signed-off-by: Anton Litvinov <[email protected]>
Signed-off-by: Anton Litvinov <[email protected]>
Signed-off-by: Anton Litvinov <[email protected]>
Signed-off-by: Anton Litvinov <[email protected]>
… of found nodes Signed-off-by: Anton Litvinov <[email protected]>
03c6753
to
cdc4644
Compare
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically closed because it has not had activity for a long time. If this pull request is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions. |
Summry of task:
Essentially, the program should get the connection parameters from the API, raise the connection and make sure that it works.
Establishing a VPN connection to wireguard must be done through the wg+gvisor combination, because raising a real network interface is not convenient especially in could environments, so a VPN connection that works entirely from code would be very useful.
Implementation notes:
Check of provider's functioning is done by requesting to http://107.173.23.19:8080/test
How to build
go run mage.go buildProvChecker
Example of use
.\build\myst\myst.exe --provchecker --log-level=error daemon
Example of use #2 (with postgres - to save results of scan into table)
.\build\myst\myst.exe --provchecker --log-level=error --checker.dsn="host=yyy user=mypguser password=xxx dbname=myst_nodes port=5432 ss
lmode=disable" daemon
Api
http://localhost:4050/prov-checker?id=0x020dd683990895d0f81a47702161f1d29d209976
Response:
{"status":true,"error":null,"provider_id":"0x020dd683990895d0f81a47702161f1d29d209976"}
Batch mode (check many providers):
Response:
Batch mode #2 (check all providers of a given country or gloabally):