09:46 <miragebot> [mirage] samoht pushed 3 new commits to master: http://git.io/vUy4x

09:46 <miragebot> mirage/master 51f5245 Thomas Leonard: Add --no-depext flag...

09:46 <miragebot> mirage/master 459ac22 Thomas Leonard: Set UPDATE_GCC_BINUTILS=1 for Travis

09:46 <miragebot> mirage/master 6b4c6e7 Thomas Gazagnaire: Merge pull request #402 from talex5/no-depext...

13:02 <m_> hi all, how a mirage unikernel can get information about its resource usage e.g. cpu load, memory, etc?

13:46 <avsm1> m__: the easiest way is to query the OCaml Gc module for memory

13:47 <avsm1> CPU requires some support from the runtime, but shouldn't be hard to add to minios. A thread on mirageos-devel or an issue would be useful, as it's a nice thing to have. The obvious alternative is to use the hypervisor monitoring APIs to check on the unikernel CPU/net/block stats from outside (e.g. via xentop)

13:49 <m__> thanks, what would be the Gc module fucntion for memory?

13:51 <m__> and is there any online guide for uning hypervisor APIs in mirage apps?

13:51 <Drup> m__: https://github.com/ocsigen/eliom/blob/master/src/lib/server/monitor/eliom_monitor.ml#L71-L89 that's the "monitor" thingy in eliom, you can use this part directly

13:52 <Drup> (well, modulo tyxml)

14:50 <miragebot> [mirage] samoht pushed 2 new commits to master: http://git.io/vU9sA

14:50 <miragebot> mirage/master b7d6486 Thomas Gazagnaire: Update CHANGES

14:50 <miragebot> mirage/master 6b0606f Thomas Gazagnaire: Merge pull request #403 from samoht/master...

14:51 <miragebot> [mirage] samoht deleted v2.5.0 at d3ee2b4: http://git.io/vU9GR

14:52 <miragebot> [mirage] samoht tagged v2.5.0 at master: http://git.io/vJ6Pk

14:52 <avsm1> m__: unfortunately no online guide about those APIs. They're all a bit undocumented, but a prod on mirageos-devel@lists.xenproject.org will unearth the ones you need

15:21 <thomasga> anyone already used conduit+tls for client call?

15:21 <thomasga> (I'm struggling to make the 3rd argument of the Conduit functor)

15:22 <hannes> thomasga: for unix, the cohttp has an example thereof

15:23 <thomasga> Drup: for mirage-www we have something similar: https://github.com/mirage/mirage-www/blob/master/src/stats.ml

15:23 <thomasga> (available at http://www.openmirage.org/stats/gc)

15:23 <thomasga> hannes: for xen

15:24 <hannes> thomasga: maybe talex somewhere? btw, https://github.com/ocaml/opam-repository/pull/4094 is green..

15:25 <thomasga> ok, I'll merge it then :-)

15:25 <hannes> cool, won't help any mirage, though..

15:26 <thomasga> as long as the constraints are ok for the other packages that's fine

15:26 <hannes> they are..

15:26 <hannes> according to my limited knowledge..

15:27 <thomasga> would be less packages to release in one chunk for the mirage release

15:27 <thomasga> so that's good

15:27 <hannes> but nc-0.4 requires mirage-no-xen | mirage-xen & entropy-xen > 0.3 (which is not in opam)

15:27 <hannes> thus, all mirage-xen people will not get nocrypto-0.4

15:27 <thomasga> yup, I saw that. should be fine

15:27 <hannes> and after 4094 I'll do another simple one

15:28 <hannes> and leave the complicated things to you ;)

15:28 <thomasga> np :-)

15:30 <thomasga> hannes: merged, can you remove the packages from mirage-dev?

15:32 <hannes> thomasga: yes

15:33 <hannes> thomasga: well, only after you merged your updated mirage checksum there..

15:34 <thomasga> hannes: done

15:52 <thomasga> hum that's annoying, conduit_mirage and TLS still don't go well together

15:53 <thomasga> (server-side TLS is ok as we don't need conduit anymore)

15:54 <hannes> thomasga: well, conduit hasn't been updated for the tls-0.5 / nocrypto-0.4 releases... what is the intended API/idea there?

15:55 <thomasga> the conduit API needs some clean-up … I was hoping we could avoid doing that before the TLS release, but well… I'll see what I can do :-)

16:09 <hannes> thomasga: in opam-repo, 4095 [tlstunnel] and 4096 [gmp-xen, zarith] also are green.. happy to update the mirage-dev removal (81) when you merge opam-repo