albatross/packaging/Linux/README.md

# systemd service scripts

these are preliminary and just here to let people play with `solo5-spt`, the seccomp-enabled backend for [Solo5](https://github.com/Solo5/solo5) on Linux.
Note: The socket paths are hardcoded relative to the RuntimeDirectory (tmpdir).
If you modify `Vmm_core.socket_path` you must modify the corresponding `.socket` file(s) in this directory.

1) You need to build the `albatross` tooling in this repository
2) To run unikernels, you need to build and install solo5-elftool and at least one of the tenders: solo5-hvt and solo5-spt. They can be installed somewhere in PATH or in /var/lib/albatross/.
2) You need to build a binary with one of the tenders (solo5-hvt, solo5-spt) to deploy.
3) See [`install.sh`](./install.sh) for commands required to deploy it.
4) `sudo journalctl -fu albatross'*'.service`
5) ideally, once the services are up and running, you would be able to issue this command to deploy a unikernel:
   `sudo albatross-client-local helloworld /path/to/hello_world.spt`
systemd services, based on ee49c6240aa2cf2c9dac47eff6c751ce8c17efb5 by @cfcs 2019-11-21 12:29:22 +00:00			`# systemd service scripts`

			these are preliminary and just here to let people play with `solo5-spt`, the seccomp-enabled backend for [Solo5](https://github.com/Solo5/solo5) on Linux.
Systemd socket activation (#43) * Use systemd socket activation * Pass a new command line argument --systemd-socket-activation to the daemons if running on Linux * Install .socket files * Systemd services depend on their sockets * Implement sd_listen_fds in OCaml * Set FD_CLOEXEC in sd_listen_fds * README: add comment about socket paths * Linux systemd scripts: Rename albatross_stat -> albatross_stats 2020-11-26 11:06:28 +00:00			`Note: The socket paths are hardcoded relative to the RuntimeDirectory (tmpdir).`
			If you modify `Vmm_core.socket_path` you must modify the corresponding `.socket` file(s) in this directory.
systemd services, based on ee49c6240aa2cf2c9dac47eff6c751ce8c17efb5 by @cfcs 2019-11-21 12:29:22 +00:00
Update Linux packaging * Update README: Names of binaries have changed, CLI interface as well, add instructions for installing tenders... * Install an empty log * Add assertion in albatross_log.service that the log file exists 2020-11-10 10:02:17 +00:00			1) You need to build the `albatross` tooling in this repository
			`2) To run unikernels, you need to build and install solo5-elftool and at least one of the tenders: solo5-hvt and solo5-spt. They can be installed somewhere in PATH or in /var/lib/albatross/.`
			`2) You need to build a binary with one of the tenders (solo5-hvt, solo5-spt) to deploy.`
systemd services, based on ee49c6240aa2cf2c9dac47eff6c751ce8c17efb5 by @cfcs 2019-11-21 12:29:22 +00:00			3) See [`install.sh`](./install.sh) for commands required to deploy it.
			4) `sudo journalctl -fu albatross'*'.service`
			`5) ideally, once the services are up and running, you would be able to issue this command to deploy a unikernel:`
Update Linux packaging * Update README: Names of binaries have changed, CLI interface as well, add instructions for installing tenders... * Install an empty log * Add assertion in albatross_log.service that the log file exists 2020-11-10 10:02:17 +00:00			`sudo albatross-client-local helloworld /path/to/hello_world.spt`