-
Notifications
You must be signed in to change notification settings - Fork 567
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
RancherOS support #10
Comments
Okay, made it work by adjusting the hard-coded launch command. It would probably make sense to allow setting the frontend mode via the manager commandline? |
Currently, TCMU is not as well tested as TGT, so we haven't recommended to use it. We're working on it TGT support for RancherOS at the moment. We expect it to work in the near future. |
any updates on this perhaps ? :) |
Got to involve @SvenDowideit :) |
he seems pretty busy as we can see in RancherOS github project :) |
yup, I got so far as to add an open-iscsi service to the master services repo, and then things got busy :/ |
@SvenDowideit do you think it could be enough (open-iscsi service) to test longhorn with rancheros ? |
Now we should able to support RancherOS, longhorn/longhorn-manager@521920d Anyone can refer to the following steps to experience:
RKE
Update FLEXVOLUME_DIR before deploy longhorn
|
@niusmallnan Hey, can you provide any more guidance on this? Still not super clear to me. I have 3 RancherOS nodes, all 3 running ubuntu console.
What exactly am I supposed to do with Thanks. |
@DeviantEng We haven't had RancherOS support in a release yet. If you want to give it try, using Starting the next release (v0.3) we will formally support RancherOS. |
@yasker Thanks for the replay. I'm still testing around with other things in Rancher 2, so I can wait for the next release (of Longhorn, I assume?). Is there an ETA on that currently? With formal support fo ROS, will that only be with the ubuntu console, or will that be with all consoles (minor thing, but just curious)? |
@DeviantEng We're targetting next month for the release. Regarding the available consoles, we will support default console as well in the release. |
Pending on default console support and (possible) user configuration-free experience. |
What's the latest on this? I would love to test Longhorn on my RancherOS Rancher cluster. |
Same here. Seems like a good alternative to NFS. |
@DeviantEng @MaxDiOrio We cannot finish RancherOS support for v0.3.0 release in time. We're trying to get done in v0.3.1 release, but it all depends on our bandwidths. We definitely should able to support RancherOS in v0.4.0 release. |
I was hoping to finally give this a try with the 0.4 release, but apparently this has moved. Will this be available by the time rancher 2.2 gets released? |
@krishofmans: |
@krishofmans Sadly it won't be available by the time Rancher 2.2 released. RancherOS support is a priority for v0.5 release. |
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Now support RancherOS longhorn/longhorn#10 longhorn/longhorn#198 Now support k3s. But sometimes it can not pass all integration tests longhorn/longhorn#434 longhorn/longhorn#436
Support integration test on RancherOS longhorn/longhorn#10 Some test failures in k3s may be caused by the high latency of status update longhorn/longhorn#436
Fixed by longhorn/longhorn-manager#242 |
TGT frontend doesn't work on RancherOS, but TCMU does (tried with these commands). Is there a way to tell the manager to use use TCMU mode?
The text was updated successfully, but these errors were encountered: