avsm changed the topic of #mirage to: Good news everyone! Mirage 3.0 released!
raboof has quit [Ping timeout: 255 seconds]
raboof has joined #mirage
copy_ has joined #mirage
ro6 has joined #mirage
amirmc has joined #mirage
talex5 has joined #mirage
avsm has joined #mirage
TImada has joined #mirage
<amirmc> Hi folks!
<demonimin> hi!
<talex5> Hi!
<lobo> hi
ricarkol_ has joined #mirage
<mato> Hi all
<avsm> greetings!
<ricarkol_> Hola
<TImada> Hi all!
<amirmc> It looks like we've got two items on the agenda for today (plus whatever else we add during the catchup). Feel free to add items as we go. https://github.com/mirage/mirage-www/wiki/Call-Agenda#16th-august-2017
<amirmc> First item is an update from talex5 about https://github.com/mirage/capnp-rpc. Over to you, talex5!
<talex5> OK. I've finally made a release of the Cap'n Proto schema compiler with RPC support:
<talex5> I've also made the first release of the RPC implementation:
<avsm> I've gone through the README and passed the tutorial
<avsm> do I get a gold star :)
<talex5> Did it work?
<avsm> I've also started writing a distributed build service using it, with a pure-CLI workflow for our CI
<avsm> it did!
<avsm> it's sort of blowing my mind actuallhy
<avsm> the build service has a logging service, and can build containers
<avsm> and the capnp object capability model is perfect
<avsm> since you connect to the scheduler, which has all the workers registered to it, and they pass in a callback that can be used to invoke build jobs directly on thenm
<talex5> Nice! Is this published somewhere?
<avsm> i've got the scheduler and worker registration working (with arm64/x86 hosts), and will try the callback magic shortly to see if i can invoke jobs on them over the cluster :-)
<avsm> talex5: do you know if there is a central register of capnp specs in the wild
<avsm> i was wondering how much i am repeating by building (e.g.) a logging service
<talex5> I don't think so. The best place to ask would be the google group: https://groups.google.com/forum/#!forum/capnproto
<avsm> thanks
<avsm> i'd forgotten about sandstorm indeed -- they have loads
<avsm> https://github.com/avsm/obi is my (very work in progress) tree
djwillia has joined #mirage
<amirmc> Nice name :)
<avsm> i'm aiming to be able to `obi submit` a job and have `obi term` give you a shell into it
<avsm> amirmc: the first release is going to be called...
<avsm> obi one!!!!
<avsm> ocaml build infrastructure, of course :-)
<amirmc> Yeah, i saw that coming
<avsm> talex5: i think this might be a simple solution for the distributed opam/mirage builds than datakit
<avsm> since the cluster can grab jobs and build a docker container locally and quite statelessly
<avsm> i'm hoping to keep everything capnp, and then export a web interface alongside the cli interface
<talex5> Could be. I'd like to get DataKit using capnp eventually too.
<avsm> yeah
<avsm> i'm not sure about conventions for e.g. authentication
<talex5> That will come with level 2 support.
<avsm> do most people authenticate their entry point to the registry daemon over TLS certs
<avsm> should i just have a convention of the registry service requiring a token for now?
<avsm> i.e. bake in authentication into the service that is the entry point
<talex5> Yeah, the bootstrap service can do traditional auth for now and then return the real capability.
<avsm> sounds good, i'll do that and then examine level2
<avsm> thanks for all the hard work with the release -- it's the first rpc service i've used that seems to genuinely add value :-)
<avsm> the capability passing is just great
<talex5> Thanks! Very happy to get feedback about it :-)
<amirmc> talex5: I assume you'd like others to try it out too. Is there a blog post in the works?
<talex5> No, but the README is fairly extensive.
<talex5> (yes, I would like others to try it out)
<avsm> i think it'll become more accessible with a few more users of it
<avsm> i'll get obi done asap
<dinosaure> hi all
<talex5> Does anyone else have a use they're thinking of trying it on?
<avsm> there's a post on https://discuss.ocaml.org/t/ann-capnp-rpc-0-1/698/6 as well btw
<amirmc> If anyone is trying it out or would like to, please get in touch with talex5. The repo is at https://github.com/mirage/capnp-rpc
<amirmc> Next item on the list is about moving the infrastructure machines. avsm, over to you!
<avsm> i've been meaning to install sandstorm for a while, have put it on my queue
<avsm> some background! we have been paying for machines at Bytemark for mirage infrastructure for a while -- on amirmc's credit card
<avsm> the bill has been getting steep, and we also want lots of IP addresses for unikernels
<avsm> so (with thanks to amirmc for loading his credit card all this time), i've cleared plenty of address space in the Computer Lab
<avsm> we now have a /24 ipv4 publically routed, and a big ipv6 allocation ,and a dedicated machine cluster and an openbsd router all setup
<avsm> i'm installing xenserver on one of the machines which should be suitable for unikernels
<avsm> and there'll be a freebsd box as well
<mato> nice!
<mato> it'd be great if we could have xen, freebsd, linux+kvm
<avsm> the gateway is routing as of 10 minutes ago, so now i am netbooting all the machines
<avsm> mato: any preferred xen distribution?
<mato> avsm: I use Debian for everything Linux :)
<avsm> i was thinking a debian box with xen, and then xenserver for more "production" services
<avsm> just attempting to find a non systemd linux distro :P
<avsm> i'll see if i can get linuxkit on there
<avsm> oh, i am also bridging ipsec tunnels into IBM, djwillia
<avsm> since we have power machines from there, and arm64 from packet.net
<avsm> so they'll all be mapped into the same infrastructure and be ready for builds
<amirmc> Just for the record, Bytemark have been pretty good to us. It was just getting pricey and there are other options better suited to what's needed. :)
<avsm> Bytemark's been brilliant, a really excellent hosting provider
<djwillia> does the mirage stuff work on POWER?
<avsm> not quite yet, but having a machine gets us part of the way there :P
<avsm> i think it's a lot easier now that arm64 is merged, so we have two arches
<avsm> ocaml does have a native backend for it
<djwillia> cool!
<avsm> but anyway, that's the update there -- the dhcpd in the cluster is running charrua-unix atm, hopefully a unikernel soon :-)
<avsm> if anyone's interested in ipv6, let me know...
<mato> avsm: Yes, with x86 and arm64 merged it should be "easy" for someone to add power
<amirmc> Thanks for the updates! We're at the end of the advertised agenda. Are there any other questions/thoughts anyone would like to bring up?
<amirmc> If not, we can bring the formal catchup to a close. Feel free to hang out and continue chatting though!
<djwillia> thanks amirmc!
ricarkol_ has quit [Ping timeout: 260 seconds]
<hannes> I'm interested in IPv6 :)
<avsm> thanks everyone!
<avsm> hannes: just getting ipv4 routing up and then will try the CL ipv6...
<hannes> btw, I setup ns0.mirage.io and ns1.mirage.io, see https://github.com/mirage/ns.mirage.io/issues/1#issuecomment-318933393
<hannes> we could switch there..
<mato> I think hannes means "I'm interested in a working IPv6 mirage-tcpip" :-)
<hannes> (currently at a lakeside in Poland)
<mato> last I remember the current status of our IPv6 support was "it builds, but no one's tried to use it"
<hannes> I'd be interested in IPv6 support for mirageos and recently found a testsuite http://www.ttcn-3.org/index.php/development/devlibraries/devlib-libipv6 :)
<avsm> handy!
<avsm> alright, i'm diving back into pf.conf and then will get to ipv6
<hannes> I've fixed ~5 bugs in the TCP/IP model (network semantics) in recent weeks (and am about to finally release my DNS thingies)
<avsm> enjoy the lakeside hannes :-)
<hannes> I do, as usual :D
<hannes> thanks for unbreaking mirage after the jbuild move! :)
<avsm> getting there -- i'll be happier once we have this build infrastructure finally in place
<avsm> decent CI seems to be an ever-moving target
<hannes> yes..
amirmc has quit [Quit: Leaving.]
talex5 has quit [Quit: Leaving]
djwillia has left #mirage ["ERC Version 5.3 (IRC client for Emacs)"]
avsm has quit [Quit: Page closed]
TImada has quit [Quit: Page closed]
ro6 has quit [Quit: Connection closed for inactivity]
copy_ has quit [Quit: Connection closed for inactivity]
ro6 has joined #mirage
trn has quit [Remote host closed the connection]
trn has joined #mirage
ro6 has quit [Quit: Connection closed for inactivity]