-
Notifications
You must be signed in to change notification settings - Fork 8
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
Replace deprecated Lwt usages #21
Conversation
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.
This looks good.
This needs changes in the daemonization of wsproxy (convert to systemd unit?) |
I like that. I would assume that this is not difficult (looking at |
|
My guess is that socket activation needs to be set up along with the service unit. |
with_fd fd_sock' | ||
~callback:(fun fd -> | ||
let iov = Lwt_unix.io_vector ~buffer ~offset:0 ~length:16384 in | ||
Lwt_unix.recv_msg ~socket:fd ~io_vectors:[iov]) | ||
let io_vectors = Lwt_unix.IO_vectors.create () in |
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.
🎊
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
What is the state of this? Can we merge this? |
The socket/service are not activated when building the packages although they seem to work fine when enabled manually. It needs more changes in the spec files |
Testing didn't go as planned: The connection to the guests are not successful when the wsproxy service is up and running, while managed by systemd. I'll debug the changes in wsproxy as xapi is correctly opening the socket (wsproxy gets run by systemd) |
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Comparison of the log format before and after:
Processing the message as malformed is not intended, have to look into it. The xapi plumbing looks good so far, however. |
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This will be done by whoever spawns us (e.g. systemd) Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
In order to use socket activation, we cannot create the sockets like we were doing before, we would have to use something like https://github.com/juergenhoetzel/ocaml-systemd |
It's not needed anymore due to systemd Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Instead of setting up a socket on startup, make the caller activate the socket and pass it as standard input. Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
This change is due to xapi-project/wsproxy#21 Signed-off-by: Pau Ruiz Safont <pau.safont@citrix.com>
Pull back changes from #21 (Update Lwt logs and remove daemonization)
Fixes #13 and also prepares the code for Lwt 5.0