Michael Vogt

@michaelvogt
94 Followers
23 Following
13 Posts
I like tea and free software
githubhttps://github.com/mvo5
@rfc1036 @pid_eins @arianvp Thanks again @arianvp for the very nice gist - I created https://github.com/systemd/varlink-http-bridge/pull/13 that should implement this "--more" streaming via json-seq and connection pipelining in the bridge now without websockets- really cool to get these kind of improvement suggestion so quickly/nicely.

Some cool news about the rust based varlink-http-bridge - its now under the systemd org and @zeenix ported it to zlink in https://github.com/systemd/varlink-http-bridge/pull/7 - many thanks!

I'm exicted to see more rust usage in the systemd org and hope it will keep growing. Help (especially from experienced rust developers) with the varlink-http-bridge is of course always welcome!

@brauner @daandemeyer I played with #barrage and wrote a bunch of async tests and its beautiful!
@rfc1036 @pid_eins @arianvp Thanks for the feedback! We have a websocket and non-websocket mode currently in the bridge (and no-websock is much nicer with e.g. curl). Its just that varlink map extremely nicely to websockets, especially things like the protocol switching in varlink. I will look harder into this though, the "more" streaming looks pretty simple in plain http and that should cover most use-cases of today.
@arianvp @pid_eins Thanks Arian for the gist! The main reason for the websocket stuff is/was the protocol switching that Lennarts mentioned. But of course your right that just for the --more we won't need it and can use http streaming or SSE. I expect that we will add either http stream or sse (or both) pretty soon to make it easier for traditional curl usage to call e.g. io.systemd.JournalAccess.GetEntries. But I also want to make sure we DTRT so this kind of feedback is much appreciated!
@Foxboron @pid_eins Yeah, sorry, its all very fresh! Fixing this now :)
@diegovsky @pid_eins Varlink streaming is supported when using the websocket, its pretty nice with the new varlink-protocol feature of systemd v260+: `varlinkctl call --more http://localhost:1031/ws/sockets/io.systemd.JournalAccess io.systemd.JournalAccess.GetEntries {}`. The regular API does not currently support streaming, I was thinking we could add it via SSE but not fully sure yet
@juliank Oh no! Sorry to hear that, all the best for you!

RE: https://mastodon.social/@amutable/115967747219090945

Today I'm super excited to announce Amutable, our new company together with @pid_eins and @blixtra.
I couldn't be happier to have @cyphar, @daandemeyer, @zbyszek, @pothos, @michaelvogt,
@rodrigo_rata, @davidstrauss as part of our team.
I've known them for a very long time and I'm very happy they are on board for the ride.
I can't wait to show everyone what we're building.
Made with ❤️ in Berlin.

https://amutable.com/blog/introducing-amutable

#amutable #linux #systemd #⊼mutable #integrity

Right on time to coincide with the end of the year I finished my #systemd259 series of posts. And I now also prepped a blog story linking to every single one of them here:

https://0pointer.net/blog/mastodon-stories-for-systemd-v259.html

Make sure to stay tuned for the #systemd260 series, most likely starting already in a few weeks!

Also, happy new year! 🎇

Mastodon Stories for systemd v259

Posts and writings by Lennart Poettering