move more assets to this host
This commit is contained in:
parent
2d10e2cc8a
commit
65cee6703a
8 changed files with 5 additions and 5 deletions
|
@ -9,7 +9,7 @@ Less than two years after the initial proposal, we're happy to present conex
|
|||
0.9.2. Pleas note that this is still work in progress, to be deployed with opam
|
||||
2.0 and the [opam repository](https://github.com/ocaml/opam-repository).
|
||||
|
||||
![screenshot](https://berlin.ccc.de/~hannes/conex.png)
|
||||
![screenshot](/static/img/conex.png)
|
||||
|
||||
[Conex](https://github.com/hannesm/conex) is a library to verify and attest release integrity and
|
||||
authenticity of a community repository through the use of cryptographic signatures.
|
||||
|
|
|
@ -5,7 +5,7 @@ tags: UI, security
|
|||
abstract: implement it once to know you can do it. implement it a second time and you get readable code. implementing it a third time from scratch may lead to useful libraries.
|
||||
---
|
||||
|
||||
![screenshot](https://berlin.ccc.de/~hannes/jackline2.png)
|
||||
![screenshot](/static/img/jackline2.png)
|
||||
|
||||
Back in 2014, when we implemented [TLS](https://nqsb.io) in OCaml, at some point
|
||||
I was bored with TLS. I usually need at least two projects (but not more than 5) at the same time to
|
||||
|
@ -189,7 +189,7 @@ them to update. This only works if each user compiles the git version anyways.
|
|||
|
||||
## User interface
|
||||
|
||||
![other screenshot](https://berlin.ccc.de/~hannes/jackline.png)
|
||||
![other screenshot](/static/img/jackline.png)
|
||||
|
||||
Stated goal is *minimalistic*. No heavy use of colours. Visibility on
|
||||
both black and white background (btw, as a Unix process there is no way to find
|
||||
|
|
|
@ -25,7 +25,7 @@ Service deployment is complex: you have to consider its configuration, exfiltrat
|
|||
|
||||
We monitored the resource usage when migrating our CalDAV server from Unix process to a MirageOS unikernel. The unikernel size is just below 10MB. The workload is some clients communicating with the server on a regular basis. We use [Grafana](https://grafana.com/) with a [influx](https://www.influxdata.com/) time series database to monitor virtual machines. Data is collected on the host system (`rusage` sysctl, `kinfo_mem` sysctl, `ifdata` sysctl, `vm_get_stats` BHyve statistics), and our unikernels these days emit further metrics (mostly counters: gc statistics, malloc statistics, tcp sessions, http requests and status codes).
|
||||
|
||||
[<img src="https://berlin.ccc.de/~hannes/crobur-june-2019.png" width="700" />](https://berlin.ccc.de/~hannes/crobur-june-2019.png)
|
||||
[<img src="/static/img/crobur-june-2019.png" width="700" />](/static/img/crobur-june-2019.png)
|
||||
|
||||
Please note that memory usage (upper right) and vm exits (lower right) use logarithmic scale. The CPU usage reduced by more than a factor of 4. The memory usage dropped by a factor of 25, and the network traffic increased - previously we stored log messages on the virtual machine itself, now we send them to a dedicated log host.
|
||||
|
||||
|
@ -47,7 +47,7 @@ Another noteworthy unikernel is `letsencrypt`, which acts as a secondary server,
|
|||
|
||||
We like to gather statistics about the resource usage of our unikernels to find potential bottlenecks and observe memory leaks ;) The base for the setup is the [metrics](https://github.com/mirage/metrics) library, which is similarly in design to the [logs](https://erratique.ch/software/logs) library: libraries use the core to gather metrics. A different aspect is the reporter, which is globally registered and responsible for exfiltrating the data via their favourite protocol. If no reporter is registered, the work overhead is negligible.
|
||||
|
||||
[<img src="https://berlin.ccc.de/~hannes/crobur-june-2019-unikernel.png" width="700" />](https://berlin.ccc.de/~hannes/crobur-june-2019-unikernel.png)
|
||||
[<img src="/static/img/crobur-june-2019-unikernel.png" width="700" />](/static/img/crobur-june-2019-unikernel.png)
|
||||
|
||||
This is a dashboard which combines both statistics gathered from the host system and various metrics from the MirageOS unikernel. The `monitoring` branch of our opam repository overlay is used together with [monitoring-experiments](https://github.com/hannesm/monitoring-experiments). The logs errors counter (middle right) was the icalendar parser which tried to parse its badly emitted ics (the bug is now fixed, the dashboard is from last month).
|
||||
|
||||
|
|
BIN
static/img/conex.png
Normal file
BIN
static/img/conex.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 6.7 KiB |
BIN
static/img/crobur-june-2019-unikernel.png
Normal file
BIN
static/img/crobur-june-2019-unikernel.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 356 KiB |
BIN
static/img/crobur-june-2019.png
Normal file
BIN
static/img/crobur-june-2019.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 260 KiB |
BIN
static/img/jackline.png
Normal file
BIN
static/img/jackline.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 6.8 KiB |
BIN
static/img/jackline2.png
Normal file
BIN
static/img/jackline2.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 12 KiB |
Loading…
Reference in a new issue