D2.2 update

Yesterday I fixed my Ocaml install and was able to install and run the Message Router. In the afternoon, @arie, @misterfish, @natacha and I convened for a demo of the MR so far. It was very good to reconnect and see some awesome progress from Alleycat. We managed to find a bug – as always, they come to me – but it seems to be a minor one and will be fixed by the end of this month. We decided on a date for delivery of D2.2: September 29th.

Here is a copy of the pad where we took notes:

2021-09-15 D2.2

  • @arie @how @misterfish @natacha

  • due date D2.2

    • september 29.
    • what to deliver exactly
      • @how does some writing
    • write topic (use D2.1 as example)
    • @how REUSE
    • list repos involved.
      • ocaml-seaboar
      • ocaml-conduit-dream
      • upsycle-router
  • state of software

  • what does it do exactly (in layman’s terms)

  • what’s next?

  • seems like messages are expiring when the service reconnects

  • which subset of spec and why, so developers know how to contribute or get interested

  • readme, how to set up & run, scenarios

  • @how: try running on different IPs

So I’ll be setting up a couple or three machines each running one message router from the demo software (MR A, B and C) so we can test across the network. @dvn would it be possible to use rhyzome to deploy these machines? My plan is to make something like a minimalist Alpine Linux setup with OCaml and the DREAM software, snapshot it, and reproduce it twice (so we have three hosts). But it would be much more efficient to have a single declarative repository with all configurations so we can easily setup/destroy the hosts on-demand. This would also help me go through rhyzome and entanglement.garden software to get started with it – I’d like in the near future to turn all my infrastructure into a declarative state, and using rhyzome makes sense to me to support DREAM software in the wild.

1 Like