With this commit we introduce two auxilary packages that are used by Capstan to support capstan package compose-remote command:
- osv.compose-remote-base # needed when preparing the image
- osv.compose-remote # needed when contextualizing instance
When composing OSv image that will serve as base for actual instances (think AMI image or Glance image) user must manually require the osv.compose-remote-base package and set bootcmd like this:
$ capstan package compose base --run "runscript /run/init; runscript /run/app"
Then she uploads the result to the cloud provider. Whenever a new instance will be run out of it, the cpiod will be started on port 10000 waiting for someone to connect. At that time, user can contextualize her unikernel like this:
The compose-remote command will automatically require osv.compose-remote package that replaces the /run/init cpiod command with dummy command that just exits immediately.
Here are the two pre-build packages to speed-up the testing: http://x.k00.fr/1m9hb | password: 815349
Once we merge this, we will upload them to the S3 repo.
With this commit we introduce two auxilary packages that are used by Capstan to support
capstan package compose-remote
command:When composing OSv image that will serve as base for actual instances (think AMI image or Glance image) user must manually require the osv.compose-remote-base package and set bootcmd like this:
Then she uploads the result to the cloud provider. Whenever a new instance will be run out of it, the cpiod will be started on port 10000 waiting for someone to connect. At that time, user can contextualize her unikernel like this:
The compose-remote command will automatically require osv.compose-remote package that replaces the /run/init cpiod command with dummy command that just exits immediately.
Related to: https://groups.google.com/forum/#!topic/osv-dev/ha_ouYegYAc
/cc @wkozaczuk