-
Notifications
You must be signed in to change notification settings - Fork 106
Call Agenda
Upcoming agenda items for the fortnightly Mirage catchups on #mirage on FreeNode IRC.
Notes from previous calls are at http://canopy.mirage.io/irclogs
(since April 2016, earlier are located at https://mirage.io/wiki/#Weeklycallsandreleasenotes)
Calls are open to all and announced on the mailing list. Dates listed here should be considered provisional.
TODO: Hannes suggests to use https://wiki.debian.org/MeetBot for future meetings or an imaginaryfriend with some topic features (and maybe voting)?
- MirageOS 4.0!?!
- Spring retreat (http://retreat.mirage.io - @hannesm)
- your item here! (please @yournick)
- solo5 security hardening in progress (@mato)
- report from our Marrakesh retreat (@hannesm, others)
- git 2.0 released
- MirageOS 3.3.0 released
- MirageOS retreat early October (see http://retreat.mirage.io, signup still open) (by @hannesm)
-
open Result
considered harmful (deprecate OCaml < 4.03.0 in favour of 4.08.0) (by @hannesm, see https://www.mail-archive.com/[email protected]/msg02967.html) - type changes in mirage-{protocols,stack}{,-lwt} (by @hannesm, see https://www.mail-archive.com/[email protected]/msg02965.html)
- solo5 renaming on the horizon (see https://www.mail-archive.com/[email protected]/msg02961.html)
- in-progress irmin tutorials: https://zshipko.github.io/irmin-tutorial/ (@samoht)
- your item here! (please @yournick)
- your item here! (please @yournick)
- visit from a mirage/qubes IRC client! (@reynir)
- (carried over from July 11th) Idea: Generating .merlin file from
config.ml
(@reynir)
- Idea: Generating .merlin file from
config.ml
(@reynir) - OCaml 4.07 is out! 🎉 (@yomimono)
- Mirage 3.1.0 released! :)
- October retreat (3-10th) http://retreat.mirage.io (@hannesm)
- bug cleaning day on Friday 4 May (@yomimono)
- interest in a mirage-handbook work sprint? (@yomimono)
-
ppx_sexp_conv
v0.11.0 considered harmful (see https://github.com/ocaml/opam-repository/issues/11852 https://github.com/mirleft/ocaml-nocrypto/issues/143) history repeating (you can read the whole thread from March 2017 at https://www.mail-archive.com/[email protected]/msg02638.html (yes, I'm tired of that. @hannesm) -- what are good ways forward?
- mirage-fs API discussion (@hannesm see https://github.com/mirage/mirage-fs/issues/20)
- Solo5 development mailing list pre-announcement (@mato)
- grant table initialization (@reynir)
- requests for comments on github issues (@yomimono, who may not be present):
- retiring xen configuration generation https://github.com/mirage/mirage/issues/893
- discussion of the future of block device configuration https://github.com/mirage/mirage/issues/890
-
https://github.com/mirage/mirage-xen/pull/4 (exposing
virt_to_mfn
) (@hannesm) - hack retreat aftermath (@hannesm)
- we used charrua-dhcp and udns-recursive-resolver for 10 days (they consumed 4 & 6MB memory at the end), looks rather stable
- new repositories (mirage-propaganda/mirage-handbook/mirage-unix/mirage-xen)
- next marrakesh retreats scheduled
- anyone interested in working on GRE?
- others also want to know which opam packages are inside a unikernel? see and discuss https://github.com/mirage/mirage/issues/896
- the next bug cleaning day is friday, 2 March (@yomimono)
- incoming splat of ci PRs courtesy of https://github.com/yomimono/autoci (@yomimono)
- Solo5 upadtes, plus what to call the refactoring/feature branch on mirage/mirage (@mato)
- update on keepalives in tcp (@djs55)
- update on solo5 developments (@mato)
- lars_kurth would like to know our official list of repos for MirageOS (is TROVE for https://xen.biterg.io/goto/fbac70861be5f69f07d68753a5ddb120) still up-to-date?
- Muen SK v0.9 released, which supports MirageOS subjects via solo5 🎉
- bug cleaning day on Friday 2nd February, coordinate on IRC (@yomimono)
- no starch press is looking for an OCaml book author (see https://twitter.com/billpollock/status/958427212293668865) - in case you're interested, it's a fine publisher --
I'd be interested in contributing towards a MirageOS book, anyone else?(@hannesm) - fosdem this weekend (@hannesm)
- Solo5 CI updates (@mato)
- Discuss the best way to set up Mirage/Solo5 OPAM constraints so that I can start merging breaking PRs (@mato)
- GSoC / Pioneer Projects may need to be updated (hannes recently updated Canopy, but it seems like https://github.com/mirage/mirage-www/wiki/Pioneer-Projects still contains data) @hannesm (by curtiousity of lars_kurth dropping by on IRC - who updated the xen project wiki to point to canopy for pioneer projects now) -- see also qubes devel thread mentioning MirageOS
- FOSDEM 2018 (3 & 4 February in Brussels) (@hannesm)
- bug cleaning days!? previous: 5th january, next: 2nd february (@hannesm)
- hack retreat 2017: 7-18th March (http://retreat.mirage.io) - pls sign up (@hannesm)
- Thoughts on providing support for Dpdk and/or SR-IOV for solo5/mirageos (@niks3089)
- next bug cleaning day: Friday 5 January, 2018 (@yomimono)
- Netmap-enabled Solo5 available!!: https://github.com/solo5-netmap/solo5/tree/netmap (@TImada)
- documentation priorities (@mk270)
- http://retreat.mirage.io (@hannesm) -- next up: 7th - 18th March 2018
- Generating core dump for Unikernel on solo5/ukvm -- update (@niks3089)
- your item here!
- meetup at 34c3: (28th December) from 14:00 on in front of the freie congress radio (CCL Ebene 1, Bankettraum 1)
- also at 34c3: yomimono will talk about library operating systems on 30 Dec at 11:30CET in Saal Dijkstra
- next bug cleaning day is Friday, 5th January 2018 (@yomimono)
- hack retreat - reports coming in, next is lining up (@hannesm)
- (ICFP paper: @samoht volunteers to drive this)
- mirage-firewall: anyone want to support Qubes 4 rules? (@talex5)
No meeting today!
- hack retreat prep (moved to top since @hannesm has to leave at 16:30)
- move old repositories to attic (see https://github.com/mirage/mirage/issues/866) (@yomimono)
- bug cleaning day: was it good?
- reminder: bug cleaning day Friday 17th November 2017, coordinated on IRC (@hannesm, @yomimono, @djs55)
- remember https://github.com/mirage/mirage-www/pull/562 ? @yomimono does.
- please sign up for the hack retreat http://marrakech2017.mirage.io (@yomimono on behalf of @hannesm)
- capnp-rpc update (@talex5)
- mirage-nat is in mirage org & released now, use it for all your ipv4 masquerading (@yomimono)
- awa-ssh is serving SSH connections! (@hannes on behalf of @haesbaert)
- please sign up for the hack retreat http://marrakech2017.mirage.io (@hannesm)
- capnp-rpc update (@talex5)
- mirage-nat v1.0 soon, should we move it to mirage org? (@yomimono)
- status of 4.05 support (@yomimono hoping for an update from @avsm)
- status of nameserver for mirage.io (@hannesm ns0.mirage.io and ns1.mirage.io are up since two months now, but mirage.io still uses gandi. https://github.com/mirage/ns.mirage.io/issues/1#issuecomment-318933393)
- upcoming MirageOS hackathon (@hannesm)
- news from ICFP/CUFP/OCaml Workshop
- wee ICFP! (@Drup)
- solo5, ARM, and mirage 3.1 (@yomimono hoping for an update from @mato)
- supporting OCaml 4.05.0, deprecating 4.03.0 (@yomimono)
- capnp-rpc update - @talex5
- capnp-rpc update - @talex5
- moving project infrastructure machines around -- Computer Lab hosting is almost live - @avsm
- forthcoming functoria/mirage releases (pending bugfixes) - @yomimono, but really a request for information from @avsm and @samoht
- proposal to improve package quality: request for comments on https://github.com/mirage/mirage-www/pull/562 @samoht
- capnp-rpc update - @talex5
- Recording IRC logs for fortnightly meetings (Does this still happen? asks @amirmc)
- capnp-rpc update - @talex5
-
dommage
and the website(s) - @mor1 - adding end-to-end tests to functoria @samoht
- removal of OS module - @djs55 @avsm have patches to eliminate it entirely, but depends on xen -> ocaml-freestanding and removal of old platform code.
- conduit/dns/tcp/cohttp release progress: https://discuss.ocaml.org/t/ann-major-releases-of-cohttp-conduit-dns-tcpip/571, merge later this week. https://github.com/ocaml/opam-repository/pull/9824 - @avsm
- https://github.com/mirage/mirage-stable is now building a smaller doc subset with only freshest packages. See here for temporary url: http://server.mirage-stable-docs.5b43e282.svc.dockerapp.io
- jbuilder porting update: (@avsm @djs55 @samoht @rgrinberg)
- overall progress: https://gist.github.com/avsm/9a7ca626f8fe2154525561d9b196ce47
- mega mirage-dev PR for conduit, dns, tcp, cohttp, charrua ready to merge (https://github.com/mirage/mirage-dev)
- https://github.com/mirage/mirage-stable also available as an opam remote (@avsm)
- docs: overhaul based on jbuilder is ongoing (@avsm)
- what libs are left?
- Netmap on Solo5-ukvm status update @TImada
- Mirage-entropy / ocb-stubblr / nocrypto
- project updates
- Solo5 status update - @mato
- massive jbuildering is reaping rewards in the form of opam-less builds - https://github.com/mirage/mirage/pull/839 @avsm @djs55
- capnp-rpc is starting to stabilise; lots of fuzz testing happening - @talex5
- Netmap on Solo5-ukvm status update @TImada
- Wodan (mirage storage) status @g2p
- other items, like yours!
- project updates
- solo5 refactor (arm? muenSK?)
- jbuilder ports?
- capnp?
- fuzzing all the things?
- irmin (and rest api)?
- dev reports: datakit, vpnkit, can we do mirage?
- AOB item (@dstolfa)
-
AFL branches are now easy to obtain for 4.04.0, which means testing Mirage libraries with AFL and Crowbar just got much easier. @yomimono suggests testing your favorite library - see https://github.com/stedolan/crowbar/issues/2 for inspiration!
-
Please help review https://github.com/ocsigen/lwt/pull/354 \o/ - @drup
-
Jbuilder working on multiple repositories now (@avsm)
-
cstruct 3.0 merging is continuing -- tedious but steady (@avsm)
-
capnp ocaml progressing (@talex5) https://github.com/pelzlpj/capnp-ocaml
-
https://discuss.ocaml.org -- use it more?
- Been experimenting with dev reports for some Moby projects using hesternus. See: datakit and vpnkit ones. Would this be useful for Mirage repo clusters? @avsm is happy to start them off and do bi-weekly. (@avsm)
- The jbuilder shift continues and more libraries are shifting. Any comments on https://github.com/mirage/mirage/issues/818 about this? The topkg/jbuilder integration now exists so releases of big things like datakit are pretty easy. (@avsm @samoht)
- welcome David Udelson from GSoc! Working on Irmin HTTP REST API. (@samoht)
- Solo5 multiarch status update. We have access to POWER hardware now thanks to IBM. (@mato @djwillia)
- Mindy and Amir are at OSCON giving lots of Miragey talks!
- canopy.mirage.io is live and is now hosted on a unikernel! Thanks, @mato! 🎉
- could run our (mirage.io/openmirage.io) very own authoritative nameserver [as unikernel] - @avsm could you give us a zone dump? (@hannesm, after talking with @mato)
- TCP is broken https://github.com/mirage/mirage-tcpip/pull/309 @hannesm (since 3.1.0)
- anyone maintaining DNS? https://github.com/mirage/ocaml-dns/issues/137 @hannesm
- issue runthrough and tagging party on 9 May 2017, time TBA (constraints welcome) (@yomimono)
- mirage-tcpip needs a rebase to reconstruct past history, is everyone ok with mirage-tcpip#270? (@avsm)
- we have POWER and ARM hosting now -- thanks IBM and packet.net! (@avsm)
- Mindy and Amir will be at OSCON talking about MirageOS 3.0 - spread the love!
- canopy.mirage.io: fix updates by 14 April or revert to GitHub wiki for pioneer projects (@yomimono)
- docs.mirage.io: almost building again, how to notify people of breakage? (@avsm)
- hackathon writeup blog post: https://github.com/mirage/mirage-www/pull/549 (@avsm @hannesm @gemmag)
- headsup from the land of OPAM: lwt-3.0 is landing soon (@avsm)
- Build system RFC (see mirage/mirage#818 and the email thread)
- MeetBot: no progress
- hack retreat was great! thanks @hannesm :) writeups?
- recent releases: mirage 3.0.1, mirage 3.0.2, tcpip 3.1.0, charrua 0.5
- mentoring and projects - please review http://canopy.mirage.io/tags/help%20needed (data at https://github.com/mirage/canopy-data) and:
- remove anything you know is outdated/not mentored
- add anything you're interested in mentoring
- MeetBot, can someone set this up?
- GSoC/Outreachy candidates
- mirageos 3 was released on Thursday 23 Feb!!!
- irmin 1.0 was released on Friday 24 Feb!!
- hack retreat: many people are traveling today
- Blog posts: who can write some and by when? (See mirage/mirage-www#513)
- hack retreat!
- docs & blog posts for MirageOS 3: see https://github.com/mirage/mirage/issues/592 for progress
- progress on Irmin 1.0
gjaldon took notes for this meeting and made them available at https://gist.github.com/gjaldon/3e29791405390c72ee19eb91a9585554 . Thanks, gjaldon!
- MirageOS 3 beta - it's so great and extant!
- revisions to introductory materials (@yomimono with thanks to @mor1)
-
opam build
in opam2 fits nicely with workflow once you've donemirage configure
- see https://github.com/ocaml/opam/pull/2822 - Migration docs for 2.x users (@avsm, as per mirage/mirage#592)
- hack retreat update
- state of tracing - @mor1 has a student who will be working with it soon
- MirageOS 3 - module types rename is done, beta release in progress - see https://github.com/mirage/mirageos-3-beta/issues/1
- CI update: bulk builds now have diffs, adding a dedicated machine for it soon.
- IRC call feedback - see the TL;DR for suggested changes: http://reynard.io/2017/01/18/MirageIRCFeedback.html and associated issue here: https://github.com/mirage/mirage-www/issues/512
- Mirage-www: @avsm has a Jekyll-shaped plan for release
- Solo5: additional backend status? Hypervisor.framework and ARM64.
- Hack retreat: http://marrakech2017.mirage.io it will be fun (30 people so far); still some open spots available!
- MirageOS 3
- outstanding pins to forks in mirage-dev: see http://pastebin.com/kG1U8xj2
- status of V1 split
- new error scheme is merged! https://github.com/mirage/mirage/pull/743
- docs wishlist & blog post volunteers
- IRC logs missing from last several meetings - last one up is from 16 November.
- CI is looking rad - check it out at https://ci.mirage.io and https://ci.ocaml.io
- update from djwillia on solo5 + Hypervisor.framework
- Hack retreat Marrakech 2017 update: still 10 spots, March 1st - 8th http://marrakech2017.mirage.io
- mirage-types API changes update & discussion (see https://github.com/mirage/mirage/issues/698). the ongoing work around improving the interface's exposure of errors via result types is our last blocker for releasing MirageOS 3, and I (@yomimono) would greatly appreciate a sense of consensus around this issue.
- FLOW.disconnect seems like a reasonable idea and unless there are objections @yomimono will attempt to include it this week.
- CI: https://ci.mirage.io now active and tracking mirage-dev and mirage/opam-repository. (@avsm)
- Transient build breakage due to https://github.com/mirage/mirage/pull/735
- Mirage disk storage library RFC (@g2p)
- Mirage feedback outcomes: I'm writing up a post about the results (https://gist.github.com/GemmaG/d7ad4149138548a622a4db2a16883cc5 - still a rough WIP) but will use the feedback to generate some actions we might want to consider in the new year. Feedback welcome! Thanks again to those who participated. (@gemmag)
- hackathon update (@hannesm)
- come back to beta1 (@mato)
- Review new workflow patches with
opam
generation (@mato requested) - Do we open our FLOW error type? https://github.com/mirage/mirage/issues/698
- MirageOS CI is now live(ish) @avsm
- Performance harness work started with Takayuki Imada, @avsm @mor1 (@avsm)
- Aarch64 interest? (@avsm)
- Ideas for new logo (@gemma-gordon)
- MirageOS 3 Update (@yomimono)
- Release schedule
- @yomimono had hoped to tag a beta on Tuesday, but is still working on API-breaking changes. Please keep eyes open for message before the end of the week. (If you want to help, see discussions on moving errors to result types and propagating them up and down chains of functors.)
- Compilers
- current master of
mirage-xen
andmirage-solo5
should be able to handle 4.04; please report bugs
- current master of
- Tests
- travis was erroneously testing only unix backend for mirage repo; now does container builds for unix/xen/virtio/ukvm
- progress on using datakit-ci for mirage?
- @yomimono: I see that https://github.com/avsm/mirage-ci exists, would be nice to hear from @avsm about its status
- @avsm: infrastructure fails everywhere, am provisioning new bare metal machines for the CI to run reliably, via Scaleway (x86) and packet.net (ARM)
- Compiler hacking - see http://reynard.io/2016/11/16/CompHack.html for a writeup
- anything that needs more work that participants want to draw attention to?
- Performance harness - Takayuki Imada, Richard Mortier, @avsm to work on this for Mirage3 to run on an ongoing basis (issue to follow)
- Solo5
- TL;DR FreeBSD/bhyve is stable, Google Compute Engine support via
solo5-mkimage
- Consider doing a speculative refresh of the Solo5 C interfaces now, so that we go through any churn before 3.0 release rather than after?
- TL;DR FreeBSD/bhyve is stable, Google Compute Engine support via
- Release:
- 3.0 schedule?
- ocb-stubblr, coinstallability now possible?
- http://docs.mirage.io in good shape
- twiopam refreshed - https://gist.github.com/avsm/ac486f007c7ab2803b6838c97fedd07c
- Community
- please fill in the anonymous google form with your feedback on the mirage call/catchup and general mirage issues. We've had 11 responses so far (thank you to those who participated!) but I have reopened it in the hope that we might get some more - tell me your views! (GemmaG)
- Community
- please fill in the anonymous google form with your feedback on the mirage call/catchup and general mirage issues. It will be closed on Monday 24th October. (from GemmaG)
- compilers to target for MirageOS 3
- MirageOS 3 API
- fruitful mailing list conversation on errors: https://lists.xenproject.org/archives/html/mirageos-devel/2016-10/threads.html#00072
- in the absence of other concrete proposals @yomimono will add to @hannesm's PRs for network-error & attempt to make a usable package set this week
- hannesm: some more thinking regarding exact/open/closed variants, also private comes to mind, see https://lists.xenproject.org/archives/html/mirageos-devel/2015-02/msg00063.html (I recently added
>
to functions here, then>>=
worked again) -- but shouldn't prevent 615 from being merged, we can iterate - hannesm:
DEVICE
lifecycle, esp. who callsdisconnect
? switch toLwt_switch
? see ml post
- MirageOS 3 targets
- FreeBSD support via bhyve is coming along great thanks to @mato, @hannes, and @ricarkol's hard work
- QubesOS currently stalled as @yomimono is distracted
- Update on MirageOS announcement activity
- MirageOS 3 API changes:
- error handling
- standardise on rresult?
- hannes notes:
result
in mirage-types, define polyvar of error at top level (outside the module types) including app_error
;rresult
good for implementation libraries- yomimono: would be great to see proposals for specific polyvars there from someone who's used this style in a similarly general context
- device connect
- Mirage-dev status
- 32bit testing anyone (on ARM)? Travis scripts using a 32bit compiler?
- anyone already using 4.04?
- (plan as yomimono understands it is to move support from 4.02/4.03 to 4.03/4.04 when 4.04 is released; it would be great to shake the bugs out early)
Mirage 3.0
- Late Sep release...
- items for consideration: https://github.com/mirage/mirage/issues/571
- versioning of library dependencies - can someone work on this? https://github.com/mirage/mirage/issues/499
- tracking contributors - updated TROVE list to get stats
- rethinking runtime information passing?
- we have CI!
Solo5
- Solo5 tasks relevant for Mirage 3.0: https://github.com/Solo5/solo5/issues/82
- @djwillia: Upcoming blog post about UKVM mentioning Solo5? Demonstrating how easy it is to add new backends with Mirage 3.0...
Pioneer Projects
- Thanks for moving them over to Canopy, Hannes! (they are now here http://canopy.mirage.io/Projects)
- Can everyone check any projects that they are mentoring to ensure they are up to date if not?
- Can someone check tags? I used active project, head wanted for open ones, project done for finished ones. I also grouped some (like interfacing C and Irmin) which should be ungrouped and each subproject should have a slightly longer description.
- Do we need more metadata in there? atm the
author
is either the person proposing/mentoring that project or the person doing that project, clearly we should record both. I removedDifficulty
. See https://github.com/Engil/Canopy/issues/60 for feature requests - Time to add newly proposed projects?
Propositions for new projects from @drup:
- Unikernel gallery:
- js_of_ocaml + Functoria
- High level devices: Flexible API to cover all use cases for high level tasks
Some suggestions for specific levels include:- deprecate mirage-seal
- DNS server
- syslogd device
- Unikernel gallery:
Canopy use at ICFP
- Features/elements we need for liveblogging/using Canopy during ICFP
Library Tracker
Mirage 3.0
- items for consideration: https://github.com/mirage/mirage/issues/571
Solo5 @DJWillia @mato
- Wishlist for Mirage 3.0 - where best to put these? Add to above issue?
Library tracker
Pioneer Projects
- Placement and details:
- Move wiki content to canopy/other page that is easier to see? https://github.com/mirage/mirage/issues/569#issuecomment-235851380. @engil looking at some canopy updates relating to ICFP liveblogging in next few weeks - could add these features too (
wanted
,in progress
or similar) - Move projects to issue trackers and track them that way?
- Move wiki content to canopy/other page that is easier to see? https://github.com/mirage/mirage/issues/569#issuecomment-235851380. @engil looking at some canopy updates relating to ICFP liveblogging in next few weeks - could add these features too (
Propositions for new projects from @drup:
- Unikernel gallery:
- js_of_ocaml + Functoria
- High level devices: Flexible API to cover all use cases for high level tasks
Some suggestions for specific levels include:- deprecate mirage-seal
- DNS server
- syslogd device
General management/tracking of projects @GemmaG
Difficult to follow which issues are most important/short term/longer term - Could use labels, assignees and milestones more effectively. See very very initial/basic example of how I'm going to start tracking OCaml Labs projects: https://github.com/ocamllabs/Projects/issues
Will be easier to surface easy skill-level tasks for others in community to work on etc.
ICFP
- Not Mirage-specific, but anyone heading to ICFP/OCaml Workshop/ML etc etc might want to add info to this very large schedule (WIP) spreadsheet so we can all make sure we meet up/help eachother where we can with talks/workshops https://github.com/ocamllabs/Projects/issues/9 @sgrove
- Mirage meet at ICFP!
- Beginners tutorial for those interested... perhaps during OCaml workshop/CUFP sometime...
Quality and Test
Mirage 3.0
- Solo5/mirage-www
Library Tracking
Mirage.io Updates
- mirage.io letsencrypt certificate - automate this via ACME?
Quality and Test
Mirage 3.0
- ocamlfind predicates; support for stuff like https://github.com/pqwy/mirage-os-shim
- tracking issue should be up by the meeting, or shortly after
- solo5 merged!! good job, everyone!
- next stop: solo5/mirage-www
Hackathon Recap
- what's ongoing and needs attention?
- PCLOCK / MCLOCK DEVICE + merge
Library tracking
Mirage.io updates/improvements
- Added a few points that could be tackled: https://github.com/mirage/mirage/issues/569
Quality and Test
Mirage 3.0
- numerous breaking changes merged since last call
- implemented but yet to merge: removing CLOCK in favor of PCLOCK/MCLOCK
- some desired features still up in the air -- it's not clear (to yomimono, anyway) how to implement them
- specification of version numbers for dependencies
- removing the need to invoke opam from the mirage front-end tool
- some features may or may not be a good idea
- pulling the source of ultimate truth on APIs out of
mirage/mirage
and into implementation libraries
- pulling the source of ultimate truth on APIs out of
- some features have a clear path, but aren't yet implemented
- result types and pp's instead of polyvars and unprintable error types
- the resultant log changes
- efficiency improvements like
read_into
for input functions - removing unneeded dependencies (CLOCK, CONSOLE, id)
- get entropy (and seed randomness) once (related: random interface (proposal here))
- some metaissues
- it's difficult to do large breaking changes, which some items above are attempts to address
Solo5
- on track?
Hackathon
- Weds 13th July, 25 people signed up for day - please sign up if you haven't yet
- Demos for event itself?
- Pioneer Projects - up to date, can we add some relevant projects there?
- Projects being worked on for event:
- Solo5/unikernel/Mirage integration
- NickB would like to work on uboot+ocaml+mirage for the Pine64
- Qi Li - might demo his unikernel with tls for ARM cubietruck
- Lots of Docker-related projects:
- Dave wants to work on VPNkit/Windows/Mirage via a new Lwt engine that is Windows friendly
- ThomasG/L and the interns and Anil will continue to make progress on the CI system, tailored for Mirage
- IanC has been helping retire mirage-xen-arm-builder in favour of an Alpine/Moby-based ARM distro, which now works on the Cubieboards.
Outreachy
- how's syslog?
Quality and Test
- Docker containers
- Datakit prototype progress
- Windows support https://github.com/fdopen/opam-repository-mingw/
native mirage on Windows is now quite easy - CI via datakit in long term - TWiOPAM: changelogs, integrate into Dashboard, Canopy
Mirage 3.0
- mirage minor release that places upper bounds on packages during the OPAM install, and then work on breaking up the mirage-types into the new revisions.
- release manager?
- mirage-types - implement 2 versions of an interface simultaneously?
- Split API definitions out from mirage/mirage repo and depend on mirage-block and mirage-flow
Solo5
- ocaml-freestanding
- sync up with OPAM 2.0 plans
- Upcoming combined blog post: "porting mirage to a new platform" - to time with MirageOS hackathon in July?
4.03 flambda testing
- Upcoming steps/docs from thomasg?
Hackathon
- Doodle favours the day of Friday 15th July (closely followed by Thursday and Wednesday). Thoughts on having a 2 day hackathon?
- Booking venue this week - will post to mailing list
Outreachy
-
Quality and Test
- Docker container builds: OPAM2 and DataKit
- Twiopam WIP for tracking releases
-
Mirage 3.0 - breaking APIs
-
V1
andV1_LWT
module renaming -
error
types with Result.result - break up
mirage-types
into a package-per-module type - API changes: include multiple versions of an API in 'mirage-types'
- changes to semantics of functions in low-level module type defs
-
-
Solo5 - structure of mirage-platform
-
4.03 flambda testing
-
Pioneer Projects/Outreachy
- Outreachy starting this week
- Theo working on logging
-
Releases
- topkg
- bos
- fpath
- tyxml
-
Updates
- rresult
- fmt
- logs
-
MirageOS Hackathon
- Cambridge, mid June
- 20ish people
Reproducible Builds
- Hannes' suggestion: https://reproducible-builds.org/who/
- experiments validating that we generate reproducible virtual machine images
- website: https://mirage.io/wiki/reproducible
- MirageOS and QubesOS integration -> ppx_sexp_conv removal -> updated to support 4.03
Mirage Dashboard
- Handling lwt exceptions
- example/tutorial (Joel had trouble finding one)
MirageOS security advisory
- upgrade to mirage-net-xen>=1.4.2
Anything further to add?
Logging support
- small wiki page with examples/details about features? Thomas L
MirageOS 3.0
- breaking all the APIs
- logging and error reporting - is this sufficient?
- schedule? release engineer? press release via xenproject/LF?
- via @samoht https://github.com/pulls?page=1&q=is%3Aopen+is%3Apr+user%3Amirage+sort%3Acreated-asc https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3Amirage+sort%3Acreated-asc
Future hacking evening
- pick a driver/document and understand/add tests to it
- Code review - combined with a hacking evening - during June when Daniel is visiting Cambridge?
4.03 flambda testing?
- Shell issue https://github.com/ocaml/opam/issues/2255
topkg beta
- testing and thoughts?
Outreachy
- starting from 23rd May so will have some more blog posts soon
Releases:
-
Release of 2.9.0 - mirage command-line tool (improving tooling around logging)
- extension of the work started by Thomas Leonard at MirageOS hackathon and Drup's comments
-
mirage-net-xen releases and implications
-
OCaml 4.03 porting progress and flambda tests
Updates:
-
Mirage-dashboard update:
- mirage-dashboard update - now has a homepage, json and cli app. Hoping to wrap in own unikernel soon. http://rudenoise.github.io/mirage-dashboard/
-
Canopy: Engil worked on improving CSS, bugfixes and PR reviews
-
Solo5 Release - gone well?
-
Security
General:
-
Information retrieval
- OCaml Labs wiki ocaml.io: short blog updates pointing to larger/maintained wiki pages. Not taking over mirage.io but will link to relevant ocaml-mirage related projects/updates.
- mirage.io
- unikernel wiki? To account for non-ocaml specific updates/projects
-
Blog posts:
- Hackathon blog post - Mindy - PR in progress for mirage.io
- Pre-OSCON mirage post for Hacker News... AFL? HardCaml?
- HardCaml blog added to ocaml.io
- blog post re. improved logging? Thomas G and Thomas L? (see below)
- are we going to link to others' blog posts e.g . Arnaud http://abailly.github.io/posts/mirage-os-newbie.html
-
Information retrieval
-
Quality and Test
- Bulk builds
- Bytecode-only tests status
- flambda 4.03 testing
-
Improving errors and logging
- Logs vs error handling support - separated and merged?
- Solo5 status - released :)
- EC2 status - STARTED https://github.com/mirage/mirage/pull/497
-
Missing strtod
- Annoying bug https://github.com/mirage/mirage-platform/issues/118
-
Mirage 2.8.0 release with tcp/ip
-
Hackathon blogs
- Got various trip reports/blog posts from members - thanks!
-
Libraries
- mirage-dashboard some progress. Hannes set up an account to watch Mirage-related projects on GitHub in the meantime
- canopy status - has language specific highlighting and RSS. Tags?
- ARM images for Alpine Linux status
- camlp4 - any remaining libraries?
- mirage-rump port started?
- topkg status?
-
ocaml-git and irmin new release?
-
SSL expiration - switch to letsencrypt?
- about those calls (information retrieval) http://lists.xenproject.org/archives/html/mirageos-devel/2016-04/msg00006.html
- Quality and Test
- bulk builds: Needs volunteer to work on nice HTML
- status of Bytecode-only tests for each PR
- any 4.03 (flambda) experience/testing?
- Improving errors and logging: http://canopy.mirage.io/Posts/Errors (@talex5)
- How to merge before bitrot
- Adding Logs support requires changes in Functoria (https://github.com/mirage/functoria/pull/55)
- https://github.com/mirage/mirage-dev/pull/107
- solo5 status?
- rumprun bitrot https://github.com/mirage/mirage/issues/524
- status EC2: ignore command line https://github.com/mirage/mirage/pull/497
- missing strtod https://github.com/mirage/mirage-platform/issues/118
- libraries
- mirage-skeleton now executes built unikernels (and something is broken?)
- tcp/ip: icmp module type https://github.com/mirage/mirage/pull/523 https://github.com/mirage/mirage/pull/531 https://github.com/mirage/mirage-tcpip/pull/193 https://github.com/mirage/mirage-tcpip/pull/197 (@yomimono)
- Canopy status (user-provided markdown data) -- (now with tags and feeds!?) -- make a plan to move mirage.io to canopy?
- Dashboard status (git repo overview)
- arm images (Dave Tucker working on Alpine-based image which may remove maintenance burden of large image)
- camlp4: release cstruct-2.0 (ppx only)?
- related:
cow.syntax
appears to have gone, is there a functional equivalent to port all that content to?
- related:
- syslog reporter for logs library (@verbosemode @wiredsister)
- Unikernel install party
- ideas about applications: deployment matrix? EC2? home router?
- MirageOS end-of-year review