-
Notifications
You must be signed in to change notification settings - Fork 633
[SCP] Open port support #4490
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
base: master
Are you sure you want to change the base?
[SCP] Open port support #4490
Conversation
* [SCP] open port support * [SCP] open port support * Create __init__.py * Create instance.py * [SCP] open port support * [SCP] open port support * [SCP] open port support * [SCP] open port support * rollback
* [SCP] open port support * [SCP] open port support
* Firewall rul * Create VPC * Create VPC
Hi @cblmemo
Hi @cblmemo It took a while because I was very busy with various task at my company. I completed the smoke test. I did the following command as you guided.
I needed AWS credentials but I completed it like this: (sky) ubuntu@ip-172-31-6-181:~/skypilot$ pytest tests/test_smoke.py::test_minimal Can you merge my code without outbound ports? I will create another PR to discuss how to handle outbound ports. I am also writing for SkyPilot v2 code for SCP. I hope we can continue the discussion about SkyPilot v2 development :) |
Hi @hyoxt121 ! Thanks for the update. This is exciting. For smoke test, I mean can we have some scp open port related tests like this? skypilot/tests/smoke_tests/test_cluster_job.py Lines 654 to 667 in 2dba50f
|
Hi @cblmemo I have tried to run my test code but the test case is skipped. So, I tested other test cases for SCP but it showed that test is skipped. I have tried to fine the reason but I am not sure what the reason is. Can you let me know how to fix it?
My test code for open port is this: |
Hi @cblmemo I added --scp to the original command
I was unable to complete the port test because I got the following errors in /tmp/scp_http_server_with_custom_ports-9dd_a201.log
The reason is that I still use SkyPilot v1 and it occurs the above error when I run the SkyPilot (v0.8.0) This will be resolved after migrating SCP code to SkyPilot v2. Do I continue to do this? I am developing SkyPilot v2 for SCP supports. So, after I complete migrating SkyPilot v2. I will be okay. I think I need to close this PR and open new PR for SkyPilot v2 for SCP support and include open port functionalities later. At this point, I think it is not easy to merge this code. Can you let me know your opinion about this? |
Hi @hyoxt121 , could you try |
Hi @cblmemo Thank you for your advice. |
Are you checking out this branch? Can you try a clean installment in a fresh new conda environment? |
Hi @cblmemo
The error while running this is legacy code error. I am developing SkyPilot v2 (https://docs.google.com/document/d/1oWox3qb3Kz3wXXSGg9ZJWwijoa99a3PIQUHBR8UgEGs/edit?pli=1&tab=t.0) for SCP support. After completing it, there will be no more legacy code error. Can you let me know if it is better to run open port test along with it after developing SkyPilot v2 for SCP with another PR? |
Hi @hyoxt121 , iiuc you need to checkout this branch ( Also, I think this is already taking parts of implementation in the new provisioner API (i.e. the v2 api), since you are calling the provision lib to open ports. I think it would be more clear to separate those two into 2 separate PR to reduce the possibilities of correlated bugs :)) wdyt? |
Hi @cblmemo |
Sounds good. Then lets merge it in the new provisioner PR. |
Open port support for SkyServe
TODO: Refactoring for SkyServe architecture
Tested (run the relevant ones):
bash format.sh
pytest tests/test_smoke.py
pytest tests/test_smoke.py::test_fill_in_the_name
conda deactivate; bash -i tests/backward_compatibility_tests.sh