···
+
maintainer: "Hannes Mehnert <hannes@mehnert.org>"
+
authors: ["Hannes Mehnert <hannes@mehnert.org>"]
+
homepage: "https://github.com/roburio/albatross"
+
dev-repo: "git+https://github.com/roburio/albatross.git"
+
bug-reports: "https://github.com/roburio/albatross/issues"
+
"conf-pkg-config" {build}
+
"conf-libnl3" {os = "linux"}
+
"cmdliner" {>= "1.1.0"}
+
"mirage-crypto-rng" {>= "0.8.0"}
+
"asn1-combinators" {>= "0.2.0"}
+
"decompress" {>= "1.3.0"}
+
"bigstringaf" {>= "0.2.0"}
+
"metrics-lwt" {>= "0.2.0"}
+
"metrics-influx" {>= "0.2.0"}
+
"http-lwt-client" {>= "0.2.0"}
+
"solo5-elftool" {>= "0.3"}
+
["dune" "build" "-p" name "-j" jobs]
+
["dune" "runtest" "-p" name "-j" jobs] {with-test}
+
["sh" "-ex" "packaging/FreeBSD/create_package.sh"] {os = "freebsd"}
+
["sh" "-ex" "packaging/debian/create_package.sh"] {os-family = "debian" | os-family = "ubuntu"}
+
synopsis: "Albatross - orchestrate and manage MirageOS unikernels with Solo5"
+
The goal of albatross is robust deployment of [MirageOS](https://mirage.io)
+
unikernels using [Solo5](https://github.com/solo5/solo5). Resources managed
+
by albatross are network interfaces of kind `tap`, which are connected to
+
already existing bridges, block devices, memory, and CPU. Each unikernel is
+
pinned (`cpuset` / `taskset`) to a specific core.
+
depexts: ["linux-headers"] {os-family = "alpine"}
+
"https://github.com/roburio/albatross/releases/download/v1.5.4/albatross-1.5.4.tbz"
+
"sha256=01201cb598b91cc50b04860cf2dda7416923e89ca23bfbb9ab310a7def9d7c63"
+
"sha512=2c4f9ae7addf46bf2695f4d9f24961b9a83d1fefa96abbf3259b5dc56cf6ebdaeb42f3e29f926ab0e28fb217c12f510c96e3e96efe59c82f061d77fb7ac64ce2"
+
x-commit-hash: "c5104fac067f63000da255a7ab24004a88fc3bef"